Claude + Fireflies
Fireflies already sits in every meeting. Connect it to Claude and the transcripts stop being an archive and start being the input to your follow-ups, briefs, and objection research.
- Category
- Conversation Intelligence
- Connect via
- MCP · API
- Data
- Read (transcripts, summaries, action items); writes go to your CRM and inbox, not Fireflies
- Stage
- Close & Expand
- Best for
- Teams on Fireflies who want their meeting transcripts to do work, from a chat or a routine
Fireflies, and why connect it to Claude
Fireflies is the notetaker that joins your calls, transcribes them, and writes the summary and action items while you are still saying goodbye. For most teams it is the cheapest complete record of what customers actually said, sitting one search away and rarely searched. The summaries get read once, the transcripts almost never.
Connecting Claude changes what that archive is for. Ask across a quarter of calls which objection came up most and get an answer with quotes. Hand Claude yesterday's transcript and get the follow-up, the CRM note, and the risk flag in one pass. The transcript becomes the input to the work instead of a file you promise yourself you will revisit.
Three ways to wire Claude to Fireflies
Three ways to wire Claude to Fireflies, from a one-click connector to a scheduled pipeline on the API.
As a connector
Fireflies runs an official remote MCP server and is listed in the Claude connector directory. In the Claude apps go to Settings, then Connectors, find Fireflies, sign in with your Fireflies account, and approve the permissions. The same connection works in Claude Code. Best for on-demand work: pull the last call with an account, draft the follow-up, ask a question across every call this month. You need a paid Claude plan for connectors.
The API, via Claude Code or the Agent SDK
For the scheduled version, call the Fireflies GraphQL API from Claude Code or the Agent SDK: each morning, fetch yesterday's meetings, draft the follow-ups and CRM notes, flag the deals where a champion hedged, and leave the batch for review. API access depends on your Fireflies plan, so check before you design around it.
Export as the fallback
No connector or API access yet? Download the transcript and paste it into a Claude Project that holds your glossary and follow-up format. Manual, but the plays are identical, and it is a fine way to prove the value to whoever approves the plan upgrade.
See every GTM MCP server Claude can connect to →
Read first, write on purposeFireflies is a read-mostly integration. The transcripts flow out, and the outputs land in your CRM, your inbox, and Slack, which is where the approval gate belongs. Let Claude read and draft freely; keep the CRM note, the task, and the sent email behind a human until the drafts have earned your trust.
What you can do once they're connected
Answers across all your calls, with quotes: which objection came up most this quarter, which competitor got named, what customers asked for.
Follow-ups drafted from the transcript minutes after the call, quoting what the customer actually said.
CRM notes that reflect the conversation instead of a rep's end-of-day reconstruction.
Discovery prep grounded in the last three calls with the account, so the next call starts where the previous one ended.
What to build with Fireflies and Claude
Each is a full playbook or skill you can ship, wired to Fireflies.
Post-call follow-up + CRM note
The signature play: transcript in, follow-up and CRM note out, before the next meeting starts.
Discovery call prep skill
Prep the next call from the transcripts of the last ones.
Meeting follow-up with a mutual action plan
Turn the agreed next steps in a transcript into a MAP the buyer will actually sign.
Weekly competitive intel digest
Mine the week's calls for competitor mentions and objections, every Friday.
Connect it, step by step
- In the Claude app, open Settings, then Connectors, and search for Fireflies. Click Connect.
- Sign in with your Fireflies account and approve the requested permissions. The connector sees the meetings your Fireflies user can see.
- Start a chat, or a Project that holds your glossary and follow-up template, and ask for a specific meeting by title, attendee, or date.
- Run one follow-up by hand and compare it to what you would have written. Fix the template before you automate anything.
- For the daily batch, move to Claude Code or the Agent SDK against the Fireflies API and schedule it, with CRM writes behind review.
Gotchas worth knowing first
- Transcripts are long and context is finite. Ask for the specific meetings the task needs instead of dumping a month of calls into one prompt, or the quote you wanted drowns.
- Transcription mangles product names, competitors, and numbers. Keep a glossary in the Project or the system prompt so Claude reads through the typos instead of repeating them.
- Connectors need a paid Claude plan, and API access depends on your Fireflies tier. Confirm both before you promise the team a daily digest.
- Recording consent rules vary by region and Fireflies has settings for them. Automating on top of the transcripts does not change who was allowed to record.
Claude + Fireflies: common questions
Does Claude integrate with Fireflies?
Yes. Fireflies runs an official remote MCP server and is listed in the Claude connector directory, so you connect it from Settings, then Connectors, in the Claude apps or in Claude Code. For scheduled pipelines, call the Fireflies API from Claude Code or the Agent SDK.
What can Claude do with my Fireflies meetings?
Read transcripts, summaries, action items, and meeting details, then work on them: draft the follow-up, write the CRM note, flag deal risks, prep the next call, or answer a question across many meetings, like which objection came up most this quarter.
Can Claude write back into Fireflies?
The connector is mostly a read path, and that is the right shape. The outputs of the plays, follow-ups, notes, tasks, belong in your inbox and CRM, and that is where you keep the approval gate.
Do I need a paid plan?
Connectors require a paid Claude plan (Pro, Max, Team, or Enterprise). On the Fireflies side, the connector works with your existing account, while API access for scheduled automations depends on your Fireflies tier.
What is the first play to run?
The post-call follow-up. Transcript in, a follow-up email and a CRM note out, minutes after the call. It is high value, low risk, and it teaches you the glossary and template fixes every other play needs.