Integrations
Webhooks·Built in

Receive signals at any endpoint

The webhook destination is the general case. Any HTTPS endpoint gets a signed JSON body per signal, and every other integration on this site that says "through a webhook" is this destination pointed at a specific tool.

What lands in Webhooks

One request per signal. POST by default, PUT or PATCH if your endpoint wants it. Auth as a bearer token, basic credentials, an API key in a header you name, or any custom headers.

Connect it

  1. In Destinations, choose Add destination, then Webhook. Paste the endpoint URL.
  2. Pick the method and the auth style. Add custom headers if your endpoint needs them.
  3. Copy the signature secret when it shows. It shows once.
  4. Use Test connection and check the request in your logs.

One signal, arriving

POST https://hooks.example.com/signalraven
{ "signalId": "…", "personName": "Marcus Feld", "personCompany": "Brightmile", "strength": 8,
"whyItMatters": "Renewal pressure at a 200-person company inside your ICP.",
"signalDetailUrl": "https://app.signalraven.ai/signals/…", "tags": { "Territory": ["East"] } }
A sample signal. Marcus Feld and Brightmile are made up.

Details

MethodPOST, PUT or PATCH.
AuthBearer, basic, API key in a named header, or custom headers.
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

  • Verify the signature the way you would a Stripe or GitHub webhook: HMAC-SHA256 over the raw body, compare to the hex after sha256=.
  • A 401 or 403 from your endpoint pauses the destination and shows an action-required note in the portal. Fix the auth, then use Test connection to resume.

Start free trial →

Related

  • n8n Point a Webhook Trigger node at SignalRaven and run any workflow on every qualified signal.
  • Zapier Catch signals with Webhooks by Zapier and send them to any of the apps Zapier connects.
  • Make Catch signals with a custom webhook module in Make and route them anywhere Make connects.