Fireflies.ai API and Integrations: Setup Guide by Plan (2026)

The Fireflies.ai GraphQL API and its MCP server come with every plan, Free included, but the native integrations do not: the pricing page lists none on Free and marks them from Pro ^[1], though a few, such as Redtail and Snowflake, need Business. On Free a developer reads transcripts at 30 requests a minute and 500 a day but cannot upload audio by API. Pro raises the API limit to 60 a minute and 5,000 a day and opens HubSpot, Salesforce, Slack, Notion and Zapier. Business adds the controls teams usually want: Integration Rules that filter which meetings sync, Autofill CRM, video files pushed to Google Drive, Box, SharePoint or Amazon S3, and a pooled API budget. Enterprise adds team-wide webhooks for a Super Admin and an admin-only Audit Logs API (beta).

What each plan unlocks for developers

Two details in that grid catch people out. New Free API users get 14 days at Pro limits, counted from the first request and tied to the account, so creating a new key does not restart the clock. On Business, the pool grows by 60 requests a minute for each paid seat, free seats add nothing, and the developer docs give the example of a 10-seat team getting 600 a minute ^[2]. By our arithmetic the Business pool reaches its 1,200 ceiling at 20 paid seats and the Enterprise pool its 2,400 ceiling at 40. No single user may take more than half the pool.

The plan step itself is simple to price. Pro costs $10 per seat per month billed annually, or $18 per seat per month billed monthly. Business costs $19 per seat per month billed annually, or $29 per seat per month billed monthly, so the move that buys Integration Rules and Autofill CRM is $9 a seat a month on annual billing, $108 a year by our arithmetic. Every teammate in the workspace is a billable seat, which matters more than the API budget for most teams; our Fireflies.ai pricing guide covers the full bill.

Step 1: Get a key and make your first GraphQL call

The key lives under Settings, Developer settings (Personal tab), or on the Integrations page behind the Get API Key button. Fireflies says to keep it on your own server and never in a web page. GraphQL requests go to one endpoint, api.fireflies.ai/graphql, as a POST request with the key as a Bearer token in the Authorization header. Live transcription streams separately through a Realtime API over WebSockets, still in beta. One schema covers transcripts, summaries, users, channels, soundbites and AI Skill outputs.

1. Copy the key and store it as a server-side secret.
2. Query transcripts to list meetings: at most 50 per call, paged with skip, filtered by date range, host, participants or channel, and searchable by keyword in titles, spoken sentences or both (keyword up to 255 characters).
3. Query transcript with one ID to pull sentences, speakers, summary fields, sentiment and talk-time analytics, attendance and audio or video URLs. The video URL needs Pro or higher.
4. Handle rate limits: a 429 response carries a Retry-After header plus X-RateLimit-Limit, Remaining and Reset headers.

Daily quotas reset at midnight UTC, not 24 hours after your first call. The minute window resets 60 seconds after its first request. Some calls carry their own ceilings on top: deleting transcripts is capped at 10 a minute, and sharing a meeting at 60 requests an hour per user. The team analytics query needs Business and admin rights. AskFred is reachable through the API too, but every question spends AI credits, a small one-time allotment per plan and then a paid pack (see the pricing guide).

Step 2: Push recordings in and get told when notes are ready

Uploads go through the uploadAudio mutation, and the first surprise is that it takes a public HTTPS URL, not a local file. Supported formats are MP3, MP4, WAV, M4A and OGG, with a 50 KB minimum. Paid plans accept audio up to 200 MB and video up to 1.5 GB. Free cannot upload through the API at all; the call returns a paid-required error. Protected files work if you pass bearer or basic credentials in the download-auth field, or a short-lived signed URL. An admin can switch uploads off for the whole organization.

Three optional fields make imports useful. A meeting date stamps an old recording with its real date instead of the upload time. Attendee emails let the finished notes reach active CRM integrations, attaching to an existing contact or creating one. A client reference ID ties the result back to your own record. Uploads and imports above the monthly limit cost $0.01 per minute, while meetings captured by the bot are never charged per minute.

Polling is the slow way. Webhooks V2 fire on three events: meeting transcribed, meeting summarized and bot joined ^[3]. You can set up to five webhook configurations, each with its own URL and event list. The endpoint must be public HTTPS, must not redirect and must answer with a 2xx within 30 seconds. Failed deliveries retry up to five times, from 30 seconds out to 2 hours. A timeout is not retried. Webhooks fire only for meetings you own; team-wide delivery needs an Enterprise Super Admin.

Step 3: Connect Claude, ChatGPT or Cursor through the MCP server

The MCP server sits at api.fireflies.ai/mcp, and the address also appears in Settings under MCP and Dev Tools. Most clients sign in with OAuth through a Google or Microsoft account, so no developer work is needed; an API key works where a client prefers one. Only the Streamable HTTP transport is supported. The older HTTP plus SSE transport is retired. It is free on every plan, and it gives an assistant tools to search and fetch meetings, returning at most 50 results per search.

Two limits deserve attention before you roll it out. First, the MCP server shares the API budget: a tool call and a GraphQL request from the same user spend the same allowance, so a busy assistant on Free can exhaust 500 daily requests quickly. Second, the AI tool sees only the meetings your account can see. On the client side, Claude needs a paid Claude plan with connectors and ChatGPT needs a Plus, Team or Enterprise account. Fireflies also lists Cursor, Devin, Figma, Lovable, Replit and others as supported clients.

Step 4: Wire up the CRM, Slack, Notion and storage integrations

Most of these need Pro or higher, and a few need Business. Meetings recorded after you connect sync automatically; older ones go across only through a manual Push Past Meetings action with a date range. Meetings a teammate has set to private never sync unless the admin is a Super Admin. Most integrations accept several configurations, so one Slack connection can send different meetings to different channels or DMs.

HubSpot and Salesforce

HubSpot receives notes, summaries, tasks and a link to the full transcript, not the transcript itself, on contacts, leads, companies and deals ^[4]. Salesforce logs notes and action items on Contacts, Leads, Opportunities and Accounts, creates Events and turns action items into Tasks. It needs a Salesforce edition with REST API access. Business adds Autofill CRM and Deal Intelligence for both CRMs. Autofill drafts field updates, spends 1 AI credit per meeting extraction and sends nothing until someone reviews it. The help center lists 13 supported CRMs, including Pipedrive, Zoho, Dynamics 365, Close, Copper and Attio. Redtail and Affinity need Business. Sales teams will find the full workflow in Fireflies.ai for sales teams.

Slack and Microsoft Teams

Connecting Slack once enables two things: notes posted to a channel or DM, and the Slack Assistant you tag as @Fireflies. Nothing posts until you create a Slack configuration naming the channel. After that, notes go out for every meeting by default. Fireflies connects to one Slack workspace at a time. The Assistant spends AI credits, can scan up to 90 days of a channel and answers only where it has been added. The Microsoft Teams app only posts notes to a public or shared channel. It does not chat.

Notion, docs and storage

Notion takes full transcripts from Pro, and OneNote, also Pro or higher, creates a new page for each meeting rather than overwriting notes. Google Drive, Box, SharePoint and Amazon S3 save transcripts in formats such as PDF, DOCX, JSON or SRT. They receive the video file instead of audio only on Business and Enterprise. On Pro they get audio. Amazon S3 and Snowflake are Business-only, and for S3 Fireflies recommends a severely restricted AWS key.

Step 5: Automate the rest and control what leaves

Zapier connects with the Fireflies API key and fires on a New Meeting trigger, with data arriving within minutes of transcription. Fireflies sets no cap on Zaps; your Zapier plan does. From Pro you can also send audio through Zapier to be transcribed. If you follow the developer guide that relies on Webhooks by Zapier, you need a paid Zapier plan, Professional or above. Make, Pabbly Connect and Relay.app are also supported, and an n8n node covers five actions, from fetching a transcript to uploading audio.

Control is where the plans differ most. On Free and Pro, admins get only workspace-level toggles: apply one team configuration or limit who edits it. Business adds Integration Rules, which filter syncing by meeting title, host, participants or type, plus granular Integration Permissions over who may connect what. Enterprise adds the Audit Logs API, in beta and admin-only, which returns events in the OCSF v1.5.0 format for SIEM tools. Each event records the actor, IP address and source, such as the API, MCP or the web app.

The bottom line

Fireflies.ai is unusually open at the bottom: a GraphQL API and an MCP server on every plan mean a developer can prototype on Free, within its 400 minutes of storage per team (a running total) and, for accounts created on or after 1 September 2026, a few transcription credits unless auto-join is on. The real line sits at Pro, where API uploads and most native integrations begin, and at Business, where a team can finally decide which meetings sync and push video files to Google Drive, Box, SharePoint or Amazon S3. Pick the plan by what must flow out, not by request counts. Then set up webhooks before you write a single polling loop.