Integrations

What's a destination

Delivery is continuous, not batched. Monitoring runs around the clock, and a signal is routed as soon as it clears qualification, typically within minutes of the engagement that produced it. That's why a destination matters more than it first appears: signals with nowhere to go sit in the portal waiting to be found, which is the slowest possible way to work them.

A destination is where signals land. Every plan includes all integrations; what differs is how many destinations you can configure (1 on Solo, 2 on Pro, unlimited on Scale).

You can route different signals to different destinations. Most teams start with one and add more as their motion matures.

Supported destinations

Slack: fastest path to first value

Best for: getting reps to act on signals in the next 60 seconds.

Setup: From your Destinations dashboard, click + Add destination → Slack → authorize the workspace → pick a channel.

What signals look like in Slack: a formatted block with the engager's headline, post snippet, scores, three talking points, and buttons for “View on LinkedIn”, “Mark worked”, and “Snooze”.

Google Sheets: the audit trail

Best for: keeping a running log, building dashboards, or feeding spreadsheets that other tools consume.

Setup: Click + Add destination → Google Sheets → authorize Google → pick or create a sheet → confirm field mapping.

Each signal becomes one row. New columns can be added later; SignalRaven respects your column order.

HubSpot / Salesforce: via webhook

Best for: pushing signals straight into your CRM as tasks, notes, or new contacts.

Setup: Click + Add destination → Webhook → paste your endpoint URL → choose the payload format (JSON, form-encoded) → authenticate with a header or token.

We'll send a POST to your endpoint every time a signal qualifies. Most teams point this at a Zapier/Make/n8n flow that routes into HubSpot or Salesforce.

Clay, Notion, n8n & MCP

Clay:for enrichment-heavy outbound: drop your Clay webhook URL and signals stream into the table you've designated. Notion: for shared queue work: connect your workspace and each signal lands as a database row. n8n: install the native node from the marketplace to trigger custom workflows. MCP: for agent-native pipelines: point your agent at the SignalRaven MCP server and signals become a queryable resource.

Routing & filtering per destination

Once you have more than one destination, you can route specific signal slices to specific places:

• Per-destination score floors: Only send 8+ to Slack; route 5–7 to a Clay nurture table; nothing 1–4
• Per-destination ICP overrides: Slack gets only tight-ICP signals; the Sheet gets everything
• Per-destination source filters: Send competitor-engager signals to one channel, keyword-driven signals to another

The point: signals never leave SignalRaven unless they match a route you've configured. No route, no noise.

Field mapping

Every destination has default field mappings, but you can customize them. The signal payload includes ~30 fields; you usually want to surface 6–10 in any single destination. Default mapping for Slack/Sheets/Notion (the most common):

• engager_name, engager_title, engager_company
• signal_score, icp_score
• post_snippet, engagement_type
• talking_point_1, talking_point_2, talking_point_3
• why_now, linkedin_url

Common patterns

• Pattern 1: One Slack channel. Start here. Get your reps reacting to signals before you over-engineer routing.
• Pattern 2: Slack + Sheet. Slack for action, Sheet for record-keeping and post-hoc analysis.
• Pattern 3: Slack + Clay. Slack for the rep, Clay for further enrichment and automation. Most mature teams land here.

Where to go next

• Signals & scoring → Understand the score and ICP breakdown that your routing rules act on
• Sources & monitoring → Tune the sources that feed all your destinations