Draft partner intro requests from Crossbeam signals with Slack approval
When a partner is active in one of your target or closed-lost accounts, this workflow drafts an email asking the partner's rep for an intro and posts it to Slack for approval. Partner overlap turns into warm intros instead of a report.
Paste this into ChatGPT, Claude or your agent tool. See the prompt
- Prospecting / Outbound
- advanced
- AE
- Sales leader
- RevOps
- Category
- Prospecting / Outbound
- Difficulty
- Advanced
- Est. cost
- Not stated by source; needs a paid Crossbeam plan with Signals API access
Works with
Problem
Partner overlap data shows which partners are working your accounts, but someone has to notice the signal, find the partner's rep and write the ask. Most of those chances, especially on closed-lost accounts, go untouched.
Setup
An n8n workflow runs every weekday at 8:45, or on a signed Crossbeam webhook, and pulls partner deal signals from the Crossbeam API. It keeps recent, in-scope events, drops duplicates and anything already handled, and looks up the matching Salesforce account with its latest closed-lost opportunity. A Claude Sonnet agent with read-only Crossbeam MCP tools, capped at three calls per account, finds the partner's account owner and shared contacts, then writes a short brief and a draft intro email. The brief goes to a Slack thread with an approve, edit or skip form. Approved drafts are sent or saved as Gmail drafts, a Salesforce task can be logged, and every outcome is recorded in an n8n Data Table.
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
You turn partner overlap signals into a short brief and a draft intro request to the
partner's account owner. A rep approves before anything is sent.
# INPUTS
- {{SIGNAL}}: the partner deal signal (partner, account, what changed, date).
- {{ACCOUNT}}: our CRM account and its latest closed-lost opportunity, if any.
- {{PARTNER_DATA}}: read-only partner tools: the partner's account owner and shared contacts.
- {{HANDLED}}: signals already handled, to avoid repeats.
# TASK
1. Skip the signal if it is older than {{MAX_AGE_DAYS}} days, out of scope, or in {{HANDLED}}.
2. Look up the partner's account owner and any contacts we share. Use at most
{{MAX_TOOL_CALLS}} partner lookups per account.
3. Write a brief: why now, our history with the account (including why we lost, if we did),
who to ask at the partner.
4. Draft a short intro request email to the partner's owner: context, the specific ask, and
what's in it for them.
# OUTPUT FORMAT
BRIEF: 3 to 5 lines.
DRAFT EMAIL: subject + body, under {{MAX_WORDS}} words.
Then post to {{APPROVAL_CHANNEL}} with approve, edit or skip.
# GUARDRAILS
- Never send without approval. Record every outcome (sent, edited, skipped).
- Don't share our pipeline details or closed-lost reasons in the email itself.
- If the partner owner can't be found, say so and stop. Replace every {{PLACEHOLDER}} before running. Works with any capable LLM and runner.
Tools
Steps
- Connect credentials for the Crossbeam API and MCP, Salesforce, Anthropic, Slack (with interactivity turned on) and Gmail.
- Fill in the settings step: organization ID, Slack channel, event types, lookback windows, confidence threshold and send mode.
- Create the n8n Data Table that stores each event's status, so handled signals are skipped on the next run.
- Leave dry run on for the first runs, so drafts only post to Slack and nothing is sent.
- Review each brief in its Slack thread and approve, edit or skip; switch on sending or Gmail drafts once the drafts are reliably good.
Results
Template with setup documentation; no outcome data.
What goes wrong
Gotchas
- The Crossbeam Signals API needs a Supernode plan or above, webhooks need Enterprise, and API reads may count toward record export limits.
- Crossbeam MCP is credit metered at about three calls per drafted intro, so keep the per-run cap low while testing.
- Partner contacts come from what each partner chooses to share; check your data-sharing terms with each partner before using them in outreach.
- Partner reps get intro requests from many vendors, so vague or frequent asks wear out the relationship. (editor note)
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
Margaux Faurie, Crossbeam (n8n template) · vendor
Source dated 2026-10-06 · last reviewed 2026-10-12. Summarized in our own words; see the source for details.