What you get
heyBTW holds the event record: who registered, who came, who brought them, and what your team learned. Your CRM keeps owners, deals and activity. This page sets up both sides so Claude can answer questions that need both, joined on a person’semail and a company’s company_domain. When you are done, Claude knows which route reaches your CRM, and your events arrive in heyBTW with their guest lists, check-ins and registration answers.
Before you start
- The heyBTW connector is added to your Claude client at
https://mcp.heybtw.com/mcpand you have signed in. See Connect. - You know which CRM your team uses, and whether your Claude client already has a connector for it.
- You know which event platform you run events on, if any.
Steps
1
Ask Claude where you stand
Say: “What is connected in heyBTW, and which route does it use to reach my CRM?”Claude calls get_workspace_overview. The first key it reads is
crm_context: connection_path, provider, status, capability_served and agent_guidance, the one rule Claude follows next. configuration.integrations.crm states the CRM in one block, and configuration.integrations.event_platforms lists Luma, Splash and Zuddl, each with connected, status, connect_url, requires and syncs.2
Route 1: use your own CRM connector in your client (first)
If your Claude client has a CRM connector, Claude uses it first for every account, deal, owner and activity question. It needs no setup inside heyBTW.Say: “For the people on this event, who owns each account in our CRM?”Claude reads the roster from heyBTW, then looks each person up in your CRM connector, joined on
email and company_domain. heyBTW cannot see that connector, and nothing read through it reaches heyBTW. Claude says which answers came from your CRM and which from heyBTW.3
Route 2: connect a CRM inside heyBTW (for attribution)
Connect Attio, HubSpot or Salesforce in the heyBTW dashboard when you want heyBTW itself to compute pipeline attribution and follow-up status. Sign in at heybtw.com (Sign In, top right), then open Integrations for your workspace.With this route,
crm_context.capability_served is true on CRM-dependent tools and agent_guidance says the CRM values in the response are heyBTW’s. Without it, those tools return null figures with a gap, never zero, and Claude says so instead of putting a number of its own under heyBTW’s name.4
Connect your event platform in the dashboard
Event platforms connect in the dashboard, not over MCP. Sign in at heybtw.com (Sign In, top right), open Integrations, and add the platform’s API key. The overview’s
connect_url links to the same page.- Luma needs a Luma Plus API key.
- Splash needs your Splash enterprise API credentials.
- Zuddl needs your Zuddl account API key.
5
No platform, or an event that lives elsewhere
Say: “Add this event to heyBTW: https://partiful.com/e/…”Claude calls create_collab with the link, then records the guest export with record_signups or gives you a create_import_link for a file. An export records what it holds at that moment; only a connected platform keeps attendance and registration answers current.
6
Check again
Say: “Check the connections again.”Claude calls get_workspace_overview and reads back
crm_context and each platform’s status as served.What each route unlocks
Pair it with your tools
heyBTW works best next to the tools you already have in Claude. Common setups:
Example: “Using HubSpot and heyBTW, who registered for the SF dinner, and who owns each of their accounts?”
What heyBTW will and won’t do
- heyBTW stores references and join keys. It never copies deal stage, owner or amount from your CRM into heyBTW.
- heyBTW never writes to your CRM and never sends, with two exceptions it names and you confirm first: a Luma invite send, and a collab co-host invitation email.
- heyBTW never adds guests to your event platform.
- heyBTW does not store your platform API keys over MCP. They go in the dashboard only.
- When a step needs a connector your client does not have, Claude tells you once which one and carries on with what heyBTW returns.