Integrations
Integrations
Section titled “Integrations”The Integrations tab connects your agent to the tools you already use. It has four sections: Calendar, Email, Note-taker, and CRM.
Calendar
Section titled “Calendar”Connect your Google Calendar so your agent can automatically join scheduled calls.
- Default mode — choose how your agent joins each meeting:
- AI Avatar — your agent attends and runs the conversation
- Note Taker — your agent silently captures the meeting
- Opt-in vs opt-out — decide whether your agent joins every scheduled call by default (opt-out) or only the ones you choose (opt-in)
Once connected, you don’t have to add your agent to meetings manually — it shows up based on your settings.
The Email section has two toggles:
- Email Notifications — when enabled, you’ll receive a summary at your registered email address after each meeting, so you always have a record of what was discussed.
- Daily Leads Digest — a once-a-day morning email ranking the previous day’s leads by priority, with a link to each conversation. It’s on by default and is sent to the workspace host. It’s skipped on days with no conversations, and carries an unsubscribe link. Switch it off here any time. See Structured Outcomes & Ranked Leads for what the leads themselves contain.
Note-taker
Section titled “Note-taker”Connect an external note-taker to bring your past and future meeting transcripts into the platform as training data.
- Enter your note-taker API key to connect
- The connection status is shown so you know it’s working
- Browse your available meetings and selectively import the ones you want
- Both past meetings and new ones can be imported
Imported transcripts become training material for your agent, helping it learn your conversational style, common questions, and typical responses. You stay in control — import only the conversations that best represent how you sell. See Transcripts for how imported calls appear once they arrive.
Fathom
Section titled “Fathom”Fathom offers two ways to connect, shown on the Fathom card:
- Connect with Fathom (one-click). When it’s available, click Connect with Fathom and approve access on Fathom’s screen — no keys to copy. You’re returned to this page and the card shows as connected. This is the recommended option.
- API key. You can still paste a Fathom API key instead — both options appear on the card, so use whichever you prefer.
Once connected either way, new meetings sync automatically, and you can browse and selectively import past meetings just like any other note-taker.
Demodesk
Section titled “Demodesk”To connect Demodesk, paste your Demodesk API key.
- Use an admin-created key for company-wide coverage. A Demodesk API key only sees the recordings of the person who created it, so a key made by a non-admin covers just that user. For an org-wide connection, have an admin generate the key.
- Transcripts require the paid Coaching & AI plan. A key from a lower plan will connect but won’t return transcripts — upgrade the Demodesk account (or use a key from a Coaching & AI seat).
- New recordings sync automatically. Once connected, completed recordings flow in on a regular poll — no extra setup. Near-instant delivery is available as an optional add-on that Demodesk’s support team provisions on request; until then, polling keeps everything in sync on its own.
Jamie is a good fit for privacy-conscious, European teams: it records meetings bot-free (nothing extra joins the call) and is EU-hosted. To connect it:
- Paste an admin-created workspace key. Jamie’s workspace key gives org-wide access, so a single admin setup covers your whole team — new meetings then sync on their own with no per-user steps. The key is validated before it’s stored; an ineligible or mistyped key is rejected with a clear reason.
- API access requires a paid plan. Jamie’s API is available on Pro, Team, or Enterprise plans — the free tier has no API, so the workspace key must come from an eligible plan.
- Optional instant delivery via webhook. For meetings to flow in the moment they finish, add Jamie’s webhook signing secret when connecting and paste the shown webhook URL back into Jamie. Webhook delivery needs a Plus+ plan and an HTTPS endpoint. Without the webhook, meetings still sync automatically on a slower polling schedule — the signing secret is optional.
To connect Claap:
- In your note-taker settings, open the Claap card and paste your Claap API key. The key is validated before it’s saved — an invalid or free-tier key is rejected with a clear message.
- After connecting, the card shows a webhook URL and a webhook secret. Copy both into your Claap webhook settings so completed recordings are sent to the platform automatically.
- New Claap recordings then flow in on their own — once a recording is transcribed, it appears alongside your other transcripts, fully searchable and ready to use as training data.
Claap requires a Pro plan or higher. The Claap API is not available on the free tier, so a free-plan key can’t be connected. If transcripts aren’t arriving after connecting, confirm the webhook URL and secret are saved in Claap and that your plan includes API access.
To connect Grain, paste your Grain API token once in the Note-taker section and click Connect. New recordings then flow in automatically, and you can browse and selectively import past meetings just like any other note-taker.
- Business plan required — Grain’s transcript API is available on Grain’s Business plan. Free and Starter tiers can’t issue an API token, so the connection needs a Business account.
- Where your calls appear — imported Grain recordings show up alongside your other meeting transcripts, in the same place and format as everything else. Both past meetings and new ones can be imported.
Krisp (webhook connection)
Section titled “Krisp (webhook connection)”Krisp connects via a webhook rather than an API key — there is no key to paste. Instead, connecting reveals two values you copy into Krisp so completed meetings flow in automatically:
- Open the Krisp card and click Connect. The card shows a webhook URL and a custom request header (an
Authorization: Bearer …line). - In Krisp, go to Settings → Integrations → Webhook and create a webhook: paste the webhook URL, add the custom request header exactly as shown, and enable the transcript-created event.
- Save. New meetings ingest on their own the moment transcription completes — nothing to import manually.
Both values are saved for you, so re-opening the card lets you reveal them again without reconnecting. Webhooks require a webhook-capable Krisp plan (the free trial is time-limited); if transcripts aren’t arriving, confirm the webhook (URL and header) is configured and that your plan supports webhooks.
Webhook note-takers (Sybill)
Section titled “Webhook note-takers (Sybill)”Some note-takers deliver meetings automatically over a webhook instead of an API key. For these, connecting is a two-step paste:
- In BuzzTrail’s Note-taker settings, open the provider’s card and paste its signing secret (it usually starts with
whsec_). BuzzTrail then reveals a webhook URL unique to your workspace — copy it. - In the provider’s own settings, add that webhook URL to its automations so completed meetings are sent to BuzzTrail.
Once both sides are set, new meetings flow in on their own — no browsing or manual import.
Sybill connects this way:
- Where to find the pieces — copy Sybill’s Svix signing secret from its dashboard, paste it into the Sybill card in BuzzTrail, then paste the BuzzTrail webhook URL back into Sybill → Settings → Integrations → Automations.
- Plan requirement — webhook automations require a Sybill Pro plan or higher. On a lower plan, Sybill won’t send meetings and nothing will arrive.
- Processing delay is normal — Sybill processes a call after it ends, so insights arrive 5–30 minutes later. A transcript that hasn’t appeared immediately isn’t a fault — give it a few minutes.
To connect tl;dv, paste your tl;dv API key (found under Settings → Personal Settings → API keys) into the tl;dv card and click Connect. Once connected, you can browse your meetings and selectively import their transcripts, and new meetings sync automatically.
- A Pro plan is required. The tl;dv API is only available on a paid (Pro) plan — the free tier is app-only and won’t connect here.
- The meeting organizer’s plan controls exportability. For any given meeting, whether it can be imported is determined by the plan of the person who organized it. If an organizer is on a plan that doesn’t allow export, that meeting is skipped with a clear reason rather than failing silently — your other meetings still import normally.
Zoom AI Companion
Section titled “Zoom AI Companion”Bring your Zoom cloud-recording transcripts and AI Companion summaries into BuzzTrail. Your Zoom admin sets this up once for the whole team, and it’s read-only — BuzzTrail never changes anything in your Zoom account.
- A Zoom admin does the setup. Connecting Zoom means creating a small read-only app in your own Zoom account, pasting a few values into BuzzTrail, and copying one webhook address back into Zoom. It’s a one-time admin task — see the full step-by-step guide: Connect Zoom AI Companion.
- Cloud recording + transcript must be on. BuzzTrail imports meetings that were cloud-recorded with a transcript. Turn on cloud recording and audio transcript in Zoom so there’s something to import; local recordings won’t have anything to bring in.
- Past and future meetings both come in. After connecting, your recent recordings are imported automatically, and new recorded meetings flow in on their own once Zoom has their transcript ready — usually within a few minutes.
Connect your CRM and BuzzTrail keeps it current after every meeting — the contact, company, and a meeting note are written automatically, and (optionally) a deal is created or advanced in a pipeline and stage you choose.
- HubSpot connects with a private-app access token (six CRM scopes). BuzzTrail matches contacts by email and companies by domain, so repeat meetings never create duplicates.
- Deal sync is off by default. Turn it on to move your pipeline forward automatically — pick create-vs-advance, choose which deal to advance when a contact has several open, and keep the “only ever move deals forward” safeguard.
- Post-meeting webhooks can send each meeting’s outcome (summary, key topics, action items, sentiment, qualification score, transcript link — plus the structured-outcome framework fields, priority tier, and resolved lead segment, and a
no_showsignal) to any tool you point them at. - The resolved lead segment travels with each lead. Who the guest is — for example Senior buyer or Student / job seeker — rides alongside the priority tier everywhere a lead leaves BuzzTrail: it’s written into the CRM meeting note, added as a Segment column in the CSV export, and included in the post-meeting webhook. It’s only sent when the conversation actually resolved a segment (never a guessed value), so older leads without one simply omit it. See Segment, tier, and routing for what a segment means and how it differs from the tier.
See the full guide: CRM Sync.
Managing Connections
Section titled “Managing Connections”You can update or disconnect any integration at any time. Previously imported transcripts remain available even if you disconnect a service.
Last reviewed: 2026-07-20. Questions? Contact hello@buzztrail.ai for assistance.