What lands in Slack
Each signal is one card. The condensed layout shows a header line with the person, their company and the urgency score, the Why now line, and a View button that opens the signal in your portal. The detailed layout adds person, company, ICP and summary sections for teams working the queue from Slack itself.
Routing rules apply per destination, so a #signals channel can take everything while #hot-pipeline takes only scores of 8 and above.
Connect it
- In your portal, open Destinations and choose Add destination, then Slack.
- Choose Connect Slack and authorize the workspace.
- Pick the channel. Pick the condensed or detailed card.
- Use Test connection to send a sample card, then set routing rules if you want a score floor or a source filter for this channel.
One signal, arriving
#signals
⚡ Marcus Feld · Director, Revenue Operations · Brightmile · 8/10
Why now: commented on a competitor's pricing thread asking how teams justify per-seat spend.
View signal →
Details
| Connection | Slack OAuth through Connect Slack. A pasted incoming-webhook URL also works. |
|---|---|
| Card layouts | Condensed (header, Why now, View) or detailed (person, company, ICP, summary). |
| Routing | Score floor, ICP threshold and source filter, set per destination. |
| Plans | Included in every plan. Solo runs one destination, Pro two, Scale as many as you want. |
Good to know
- The card links back to the signal in your portal, where the talking points and the related-signal stack live.
- One workspace can hold several Slack destinations pointed at different channels with different rules.
Related
- Google Sheets → Each qualified signal becomes one row, with fixed columns your dashboards and other tools can read.
- n8n → Point a Webhook Trigger node at SignalRaven and run any workflow on every qualified signal.
- HubSpot → Route signals through a webhook into HubSpot as a new contact, a note, or a task for the owning rep.