SIGNALRAVEN
Integrations
HubSpot·Through a webhook

Create HubSpot contacts and tasks from signals

Signals reach HubSpot through the webhook destination and a short flow in Zapier, Make or n8n that creates or updates the contact and attaches the context.

What lands in HubSpot

Whatever your flow writes. The common shape: find or create the contact by name and company, write the LinkedIn URL and the ICP persona to properties, add a note with the post summary and why it matters, and create a task for the owner with the suggested opener.

Connect it

  1. Add a Webhook destination in SignalRaven pointed at a catch hook in Zapier, Make or n8n.
  2. In the flow, search HubSpot contacts by email or by name and company. Create the contact when there is no match.
  3. Write personLinkedinUrl, icpPersona and strength to contact properties. Add a note from postSummary and whyItMatters.
  4. Create a task for the contact owner with suggestedOpener as the body.

One signal, arriving

HubSpot, contact timeline
Note: Commented on a competitor's pricing thread asking how teams justify per-seat spend. Score 8.
Task for Dana: Reach out with the suggested opener. Due today.
A sample signal. Marcus Feld and Brightmile are made up.

Details

PathSignalRaven Webhook → Zapier, Make or n8n → HubSpot.
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.

Good to know

  • A native HubSpot app with timeline events is on the roadmap. The webhook path works today on every plan.
  • Dedupe on the signal id from the Idempotency-Key header to keep retries from creating a second task.

Start free trial →

Related

  • Webhooks → A signed JSON POST to your URL for every qualified signal, with bearer, basic, API-key or custom-header auth.
  • Zapier → Catch signals with Webhooks by Zapier and send them to any of the apps Zapier connects.
  • Salesforce → Route signals through a webhook into Salesforce as a lead, a contact note, or a task for the account owner.
All integrations