> ## Documentation Index
> Fetch the complete documentation index at: https://heybtw.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect heyBTW next to your CRM and your event platform

> Two routes to your CRM, one place to connect your event platform, and what each route unlocks.

## 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's `email` 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/mcp` and you have signed in. See [Connect](https://heybtw.com/docs/mcp/connect.md).
* 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](https://heybtw.com/docs/tools/get-workspace-overview.md). 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.

Each one syncs events, the guest list, registration status over time, check-ins and registration answers, and keeps them current. This is rung 1 of the event-history ladder. See [Record who registered and who came](https://heybtw.com/docs/playbooks/record-who-came.md).

**5. No platform, or an event that lives elsewhere**

Say: "Add this event to heyBTW: [https://partiful.com/e/](https://partiful.com/e/)..."

Claude calls [create\_collab](https://heybtw.com/docs/tools/create-collab.md) with the link, then records the guest export with [record\_signups](https://heybtw.com/docs/tools/record-signups.md) or gives you a [create\_import\_link](https://heybtw.com/docs/tools/create-import-link.md) 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](https://heybtw.com/docs/tools/get-workspace-overview.md) and reads back `crm_context` and each platform's `status` as served.

## What each route unlocks

| You have | heyBTW can serve | Claude does with your own tools |
| - | - | - |
| Nothing connected | Rosters you record, lists, observations, tasks, partner overlap | Nothing CRM-side; it says once which connector would complete the step |
| Your CRM connector in your client | The same, with `email` and `company_domain` join keys on every CRM-dependent result | Owners, open deals, last activity, CRM tasks and notes |
| A CRM connected inside heyBTW | Pipeline attribution, `registered_account_pipeline`, follow-up touch status, the program funnel | Any other CRM lookup, still through your connector first |
| An event platform connected in heyBTW | Events, guest lists, check-ins and registration answers that stay current | Nothing extra |
| Luma connected with a Luma Plus key | A Luma invite send through [activate\_list](https://heybtw.com/docs/tools/activate-list.md), after a preview and your explicit confirmation | Nothing extra |

## Pair it with your tools

heyBTW works best next to the tools you already have in Claude. Common setups:

| You use | Connect it | What it adds |
| - | - | - |
| HubSpot, Salesforce or Attio | Its connector in Claude, and optionally the same CRM inside heyBTW (Integrations) | Owners, open deals and activity, joined to heyBTW on `email` and `company_domain`. Connected inside heyBTW, it also powers attribution and follow-up touch status. |
| Luma (Luma Plus), Splash or Zuddl | Inside heyBTW, under Integrations | Events, guest lists, check-ins and registration answers that stay current, plus Luma invite sends. |
| Partiful, Eventbrite or a spreadsheet | Nothing to connect: paste the event link and send the guest export | The event and a snapshot of its guest list. |
| Gmail or Outlook, Slack, Google Calendar | Their connectors in Claude | Personal invites, follow-ups and owner nudges sent from your own accounts, then recorded back in heyBTW. |

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.

## Related

* [Works with any CRM](https://heybtw.com/docs/playbooks/works-with-any-crm.md)
* [What each system knows](https://heybtw.com/docs/playbooks/what-each-system-knows.md)
* [Record who registered and who came](https://heybtw.com/docs/playbooks/record-who-came.md)
* [get\_workspace\_overview](https://heybtw.com/docs/tools/get-workspace-overview.md)
* [heyBTW MCP rules](https://heybtw.com/docs/mcp/rules.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.