Description

n8n-nodes-signalpipe

This is an n8n community node. It lets you use SignalPipe in your n8n workflows.

SignalPipe decides whether the author of a post, message or email is a real buyer for your product, and calls in a panel of three AI judges when the text is not clear-cut. When SignalPipe reads the communities you choose, each buyer the judges keep becomes a mission: the post, its author and a drafted reply for you to approve. Nothing is posted or sent without a person.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

n8n has verified this node, so it installs from the canvas on n8n Cloud and on self-hosted n8n:

1. Open the nodes panel and search for SignalPipe.
2. Under More from the community, select it and install it. The instance owner or an admin installs it once; then everyone on the instance can use it.

If it does not show up on n8n Cloud, the instance owner can turn on verified community nodes in the Cloud Admin Panel. Self-hosted n8n can also install it from Settings > Community Nodes with the package name n8n-nodes-signalpipe; see n8n’s installation guide.

Operations

SignalPipe

Signal

• Score: judge whether the author of a text is a real buyer for one of your products. Optional fields:

– Context: the post or thread the text replies to.
– Source: where the text came from (for example gmail or slack), which sets the tone of the suggested reply.
– Simplify (on by default): return only the fields most workflows branch on. Turn it off to get everything, including the drafting context.

Mission

• Get Many: the open missions (waiting for approval, needing a draft, or approved). Filter by status, product or minimum score; sort newest first or by how much the judges agreed; optionally include what a writer needs to draft a reply.
• Approve: approve the drafted reply, optionally with your edited wording. SignalPipe posts nothing; approving also tells the judges the lead was a good one.
• Reject: reject a mission that was not a real buyer. The reason you pick (spam, not relevant, wrong product and so on) teaches the judges.
• Mark as Sent: record that you posted the reply yourself, so SignalPipe follows the conversation from there.
• Upload Draft: attach a reply you wrote. The mission then waits for your approval.
• Delete: remove a mission without teaching the judges anything, for example when the post was deleted.

Product

• Get Many: the products your buyers are judged against.

The SignalPipe node can also be used as a tool by n8n’s AI Agent.

SignalPipe Trigger

• New Mission: starts the workflow when SignalPipe finds a new buyer. Filters: product, minimum score, and Only With a Draft, which waits until a mission has a drafted reply.

The trigger checks on the schedule you set. When you activate the workflow, missions already in the queue are skipped; only missions found after that start it. A test run returns the newest matching mission so you can map its fields.

Credentials

You need a SignalPipe account with an active plan (pricing).

1. On your SignalPipe dashboard, create an operator key. The key is shown once; creating a new one replaces the old one.
2. In n8n, open Credentials, choose New, pick SignalPipe API and paste the key into Operator Key.
3. Save. n8n checks the key by listing your products.

A key only works while your plan is active.

Compatibility

Built with n8n’s node CLI (@n8n/node-cli 0.49) against n8n-workflow 2.40, and runs on n8n 2.40.

Usage

Reading a Score result

With Simplify on, the node returns score, classification, panelverdict, degraded, swarmskipped, role and competitor_name. With it off, you get every field below.

| Field | Meaning |
| — | — |
| classification | buyingintent, borderline, competitormention or noise |
| score | 0 to 100 |
| panelverdict | kept, rejected (the judges said no), or notrun (the text was clear-cut on its own; see swarm_skipped) |
| degraded | true when the judges should have run but did not, for example because the month’s judgements are used up. Treat these verdicts with care |
| role | the stance the drafted reply takes |
| competitormatch, competitorname, competitor_intent | whether the author mentions one of your competitors, and how |
| swarm | each judge’s stance in a word, and whether they split |
| drafting_context | present when the text is worth a reply: what a writer, or an AI node, needs to draft one |
| plan, quotamonth, quotaused_month | your plan and this month’s judgements |

A simple rule for an If node: continue when classification is buyingintent or competitormention and panel_verdict is not rejected.

A Score call uses one of your plan’s judgements only when the three judges convene. Text that is clear-cut on its own is decided without them.

Example workflows

• Triage your inbox. Gmail Trigger → SignalPipe Score (Text: the email body, Source: gmail) → If (the rule above) → create a deal in your CRM, or post to a sales channel.
• Approve replies from Slack. SignalPipe Trigger (Only With a Draft) → Slack message with the post, its link and the draft → after you approve, SignalPipe Approve and, once you have posted it, Mark as Sent.
• Draft with your own model. SignalPipe Get Many (Status: Needs a Draft, Include Drafting Context) → an AI node writes the reply from draft_context → SignalPipe Upload Draft.

Data

The node sends the text you score, and any context, to SignalPipe at api.signalpipe.io. See SignalPipe’s privacy policy for how it is processed.

Resources

• n8n community nodes documentation
• SignalPipe guide
• SignalPipe API reference

Version history

• 0.1.3: verified by n8n, so it installs from the nodes panel. Clearer field descriptions. A mission whose reply has no stance yet now returns an empty role.
• 0.1.2: the Sales and Marketing & Content categories, as n8n’s review asked.
• 0.1.1: first release on npm. Score, missions (get, approve, reject, mark as sent, upload a draft, delete), products, and the New Mission trigger. Version 0.1.0 was tagged on GitHub but never reached npm.