SIGNALRAVEN
Integrations
Clay·Built in

Stream signals into a Clay table

Clay is where enrichment-heavy outbound lives. Signals arrive as rows in the table you designate, with the person, the company, the scores and the suggested opener already filled in.

What lands in Clay

One row per signal, with the full JSON payload available to your columns. Most tables use the person's LinkedIn URL as the key, enrich email and phone from there, and pass the suggested opener into a sequencing tool.

Connect it

  1. In Clay, add a Webhook source to your table and copy its URL. Turn on the auth token if your team requires it.
  2. In Destinations, choose Add destination, then Clay. Paste the URL and, if you set one, the token.
  3. Use Test connection. A sample row appears in the table.
  4. Map columns in Clay from the payload fields you want.

One signal, arriving

Clay table, new row
personLinkedinUrl: linkedin.com/in/marcusfeld · personCompany: Brightmile · strength: 8
suggestedOpener: Saw your question on justifying per-seat spend at renewal...
tags: { "Territory": ["East"] }
A sample signal. Marcus Feld and Brightmile are made up.

Details

ConnectionClay webhook URL. Optional token, sent in the x-clay-webhook-auth header.
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

  • Tags arrive as names, so a Clay column can branch on them directly.
  • Clay treats the webhook URL as the credential. Rotate it in Clay if it leaks, then update the destination.

Start free trial →

Related

  • n8n → Point a Webhook Trigger node at SignalRaven and run any workflow on every qualified signal.
  • Webhooks → A signed JSON POST to your URL for every qualified signal, with bearer, basic, API-key or custom-header auth.
  • Slack → Every qualified signal lands in the channel you pick as a card with the score, why it matters, and a link to the full signal.
All integrations