What lands in Make
One scenario run per signal. Make learns the data structure from the first sample, so send a test before building the rest.
Connect it
- In Make, add a Webhooks module, choose Custom webhook, and copy the URL.
- In Destinations, choose Add destination, then Webhook. Paste the URL.
- Use Test connection so Make determines the data structure.
- Add the modules that write to your CRM, sequencer, or chat.
One signal, arriving
Scenario: SignalRaven → Attio person → Slack DM to owner
Webhook: Marcus Feld, Brightmile, 8, RevOps leader
Attio: create or update person, set Signal Score
Slack: DM the owner with whyItMatters and the portal link
Details
| Path | SignalRaven Webhook → Make custom webhook → your modules. |
|---|---|
| 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
- Custom webhooks are available on Make's free plan.
- A native SignalRaven app on Make is planned after the Zapier app.
Related
- Zapier → Catch signals with Webhooks by Zapier and send them to any of the apps Zapier 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.