Route 6sense and Common Room intent spikes to the right SDR with a draft
When an account starts showing buying intent, this setup assigns it to one rep and sends them a ready-to-edit message. Intent signals stop sitting in a report nobody checks.
Paste this into ChatGPT, Claude or your agent tool. See the prompt
- Prospecting / Outbound
- advanced
- SDR manager
- RevOps
- Category
- Prospecting / Outbound
- Difficulty
- Advanced
- Est. cost
- Not stated by source
Works with
Problem
Intent data lands in a CRM view nobody checks, so some spikes get actioned within the hour and others sit for days. With several SDRs, ownership of a spike is often unclear.
Setup
An n8n flow has two entry points: a webhook for real-time Common Room signals and a schedule that polls Salesforce every few hours for account fields written by the 6sense managed package. It dedupes spikes within a day, assigns them to the Salesforce account owner or a territory SDR pool, asks Claude to draft a first touch anchored to the topics the account is researching, and creates a Slack notification plus a Salesforce Task.
Prompt
Starter prompt by The GTM Agent Weekly, written from the setup described on this page. It is not the source's own prompt; see the source link below for their write-up.
# ROLE
When an account shows an intent spike, you route it to the right rep and draft a first touch
anchored to the topics the account is researching.
# INPUTS
- {{SPIKE}}: account, intent topics, strength and date (e.g. from 6sense or Common Room).
- {{ACCOUNT}}: CRM account, owner, open opportunities, recent activity.
- {{TERRITORY_POOL}}: SDRs by territory, for accounts with no owner.
- {{CONTACTS}}: known contacts at the account with titles.
# TASK
1. If this account already had a spike routed today, stop (dedupe).
2. Owner: the account owner; if none, the next SDR in {{TERRITORY_POOL}} for the territory.
3. Pick the best contact to reach based on title and topics.
4. Draft a first touch (under {{MAX_WORDS}} words) that relates to the topics without saying
we track their research. Offer something useful, then one soft ask.
# OUTPUT
Owner, contact, topics, draft email, and a one-line "why now".
The workflow posts it to the owner in Slack and creates a CRM task.
# GUARDRAILS
- Never mention intent data or "we saw you researching".
- Skip customers in an open renewal unless {{INCLUDE_CUSTOMERS}}; skip do-not-contact.
- Drafts only; the rep sends. Replace every {{PLACEHOLDER}} before running. Works with any capable LLM and runner.
Tools
Steps
- Import the workflow and set the environment variables for instance URLs and the SDR pool.
- Create Task custom fields for spike source, intent score and buying stage, and verify the vendor field names.
- Point a Common Room outgoing webhook at the n8n endpoint for the real-time path.
- Let the scheduled path poll Salesforce for 6sense account fields.
- Run the dedup test before going live so repeated spikes are dropped silently.
Results
Workflow bundle with documentation; no outcome data.
What goes wrong
Gotchas
- The polling path returns nothing unless the intent vendor is syncing fields into Salesforce.
- It does not check whether a contact is already in an active sequence; the SDR must check before sending.
- A high-severity alert means research activity, not buying readiness, so the Claude draft is a starting point to edit.
Get 5 like this every week, free.
Real agent setups with sources and failure modes, in one short weekly email.
Free. One email a week. Unsubscribe anytime.
Source and credit
ooligo · vendor
Source dated 2026-10-11 · last reviewed 2026-10-11. Summarized in our own words; see the source for details.