What lands in Zapier
A Zap run per signal, with every payload field available to later steps. The suggested opener, the LinkedIn URL and the score are the fields most Zaps use.
Connect it
- In Zapier, create a Zap with Webhooks by Zapier as the trigger, event Catch Hook, and copy the URL.
- In Destinations, choose Add destination, then Webhook. Paste the URL.
- Use Test connection so Zapier sees a sample and learns the fields.
- Add the action steps: a CRM record, a sequencer lead, a message.
One signal, arriving
Zap: SignalRaven → Pipedrive person → Lemlist lead
Trigger: Catch Hook (Marcus Feld, Brightmile, 8)
Action: Create person in Pipedrive with the LinkedIn URL and persona
Action: Add lead to Lemlist campaign with suggestedOpener as a variable
Details
| Path | SignalRaven Webhook → Webhooks by Zapier → your actions. |
|---|---|
| Payload | JSON. 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. |
| Signing | Every 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. |
Good to know
- Webhooks by Zapier is a premium app on Zapier's side; check your Zapier plan.
- A native SignalRaven app on Zapier (triggers for new signals and finished reports, actions to look up a person or company) is planned.
Related
- Make → Catch signals with a custom webhook module in Make and route them anywhere Make connects.
- Webhooks → A signed JSON POST to your URL for every qualified signal, with bearer, basic, API-key or custom-header auth.
- n8n → Point a Webhook Trigger node at SignalRaven and run any workflow on every qualified signal.