Skip to main content

​
Connecting Your CRM or Enrichment Tools

BoothRev can connect out to your own tools — a CRM, a data-enrichment provider, or anything else that exposes an MCP server — so Rev has more context on a lead from the moment they’re claimed. This is the reverse direction of Connecting Claude to BoothRev: there, Claude connects into BoothRev to read your event data; here, BoothRev connects out to pull extra context in, automatically, in the background. This is an admin-only feature, and it requires a paid plan (Monthly or Annual) — not available on the Pilot. Setting up a connection hands BoothRev a live credential to another system, so it sits alongside team management and billing rather than event setup.

​
What it’s for

The moment a lead’s email is confirmed — whether a rep claims them at the booth or you confirm them yourself — BoothRev looks at your active connections and an AI agent decides for itself whether any of the tools you’ve allowed are worth calling for this specific person: checking your CRM for existing history on their company, or asking an enrichment tool what it knows about their role and firmographics. Whatever comes back is written to the lead’s activity timeline as a plain note, labeled with the connection it came from, so it’s something a rep can actually read — not context silently folded into a Rev output with no trace of where it came from. The next time Rev analyzes that lead, it picks the note up like any other note on the timeline. This runs once per lead, right when they’re claimed — not on every re-analysis. If your CRM or enrichment tool already had the answer, re-running “Analyze with Rev” later won’t call out again for the same person. There’s no extra step for reps or event owners to trigger this — it just happens in the background the moment someone’s claimed.

​
What it won’t do

  • It only reads from your connected tool. BoothRev never writes back to your CRM or enrichment provider through this connection — and the agent calling it is explicitly told to refuse anything write-shaped even if the tool offers it.
  • If a connection is slow, down, or simply has nothing relevant, the lead is claimed normally either way — this never blocks or delays claiming someone.
  • It’s scoped to exactly the tools you allow, not open-ended access to everything your connected server can do — and it’s capped in how much it’ll do for any one lead, so a chatty or slow server can’t run away with it.

​
Setting up a connection

Go to Admin → Connections and click Add connection.
  1. Name and server URL. Give it a name you’ll recognize later, and the MCP server’s URL (from your CRM or enrichment provider).
  2. Choose how to authenticate:
    • Bearer token / API key — paste the token your provider gives you. Good for most enrichment tools.
    • Connect (OAuth) — for providers that require an interactive login, like Salesforce’s Hosted MCP Server. Clicking Connect sends you to that provider to sign in and approve access, then brings you back to BoothRev automatically.
  3. Test the connection. BoothRev calls the server to discover what tools it exposes, and shows you each one’s description so you know what you’re allowing.
  4. Choose which discovered tools BoothRev is allowed to use. There’s no single fixed tool to pick — the agent decides at claim time which of your allowed tools, if any, are worth calling for a given lead. Read-style tools (get/search/list/lookup, that kind of thing) are pre-checked for you the first time you test a connection; anything write-shaped is never pre-checked. Review the list before saving either way.
  5. Activate the connection.
From here it runs on its own. Every call the agent actually makes is logged for troubleshooting (which connection, which lead, which tool, when, success or failure) — the log doesn’t duplicate the actual data returned, just enough to trace what happened.

​
Managing a connection

  • Test at any time to confirm it’s still reachable and re-check which tools it exposes.
  • Deactivate to pause it without deleting the setup — Rev stops calling it immediately, and you can re-activate later.
  • Rotate credentials (a new bearer token, or reconnecting via OAuth) if a token is compromised or expiring. Rotating an OAuth app’s client ID/secret clears any cached tokens and requires reconnecting.
  • Delete to remove it entirely.
You can run more than one connection at once — for example, a CRM connection and a separate enrichment connection — and each is independent.

​
A note on OAuth providers

Some providers, like Salesforce’s Hosted MCP Server, require you to register a client app with them first and paste in a real client ID and secret before you connect. Others, like Apollo, need nothing pre-registered — BoothRev registers itself with the provider automatically the first time you connect. If a provider needs a pre-registered app and you leave the client ID/secret blank, the Connect step will tell you so, rather than failing silently.