SIGNALRAVEN
Integrations
n8n·Built in

Trigger n8n workflows from signals

n8n turns a signal into whatever your workflow does next: a CRM record, an enrichment call, a drafted message, a Slack thread. SignalRaven posts to your Webhook Trigger node and the rest is yours.

What lands in n8n

A signed JSON POST per signal to your Webhook Trigger node's URL. Header auth is supported when you turn it on in n8n. The signature header lets a Crypto node verify the body before anything else runs.

Connect it

  1. In n8n, add a Webhook Trigger node, set it to POST, and copy the production URL. Add header auth if you want it.
  2. In Destinations, choose Add destination, then n8n. Paste the URL and, if set, the header name and value.
  3. Use Test connection and watch the execution land in n8n.
  4. Build the rest of the workflow from the payload fields.

One signal, arriving

Webhook Trigger, latest execution
body.personName: Marcus Feld · body.strength: 8 · body.icpPersona: RevOps leader
body.suggestedOpener: Saw your question on justifying per-seat spend at renewal...
headers.x-signalraven-signature: sha256=…
A sample signal. Marcus Feld and Brightmile are made up.

Details

ConnectionWebhook Trigger URL. Optional header auth.
PayloadJSON. Person name, title, company, location and LinkedIn URL. Company size, industry, website and summary. ICP persona, seniority, confidence and composite score. Signal type, urgency score from 1 to 10, the post excerpt, a summary, why it matters, a suggested opener, the engagement detail and the source post URL. A link to the signal in your portal, the related-signal stack, and your workspace tags.
SigningEvery delivery carries an X-SignalRaven-Signature header: an HMAC-SHA256 of the raw body using the destination's signature secret. The secret shows once when you create the destination, and you can rotate it in destination settings. Idempotency-Key and X-SignalRaven-Delivery both carry the signal id, so a retry never creates a duplicate on your side.
PlansIncluded in every plan.

Good to know

  • Published workflow templates for the common paths (signal to Slack with a drafted opener, signal to HubSpot contact) are on the way. Until then the payload fields above are all you need.
  • Retries reuse the same Idempotency-Key, so an IF node on that header keeps duplicates out.

Start free trial →

Related

  • Clay → Point a Clay webhook source at SignalRaven and every qualified signal arrives as a row, ready for enrichment and sequencing.
  • Webhooks → A signed JSON POST to your URL for every qualified signal, with bearer, basic, API-key or custom-header auth.
  • HubSpot → Route signals through a webhook into HubSpot as a new contact, a note, or a task for the owning rep.
All integrations