Connect Fireflies

Fireflies is an AI meeting notetaker. Its bot joins your Zoom, Google Meet and Microsoft Teams calls, records them, and produces a transcript, an AI summary with action items, analytics and short clips called bites. Meetings can be filed into channels (folders), shared with people outside your team, and questioned in plain language through an assistant called AskFred. StackJack talks to Fireflies through its public GraphQL API, the same interface Fireflies documents for integrations.

Connecting Fireflies to StackJack gives your AI assistant a family of fireflies_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• Find and read meetings: search by keyword, date range, organizer, participant or channel, then read the AI summary, action items, outline and attendance of any meeting
• Pull the full transcript of a meeting as spoken sentences with speakers and timing
• Get the recording: a download link to the meeting's audio or video (a link expires after 24 hours)
• Ask AskFred a question about one meeting or about many, and keep a conversation going in a thread
• See what is live: meetings in progress, and the action items captured so far
• Work with bites: list and read soundbite clips
• Look around the workspace: users, user groups, channels, contacts, AI App outputs, team analytics, audit events and automation rule logs

It can also make changes, on the Pro tier:

• Tidy meetings: rename a meeting, move up to five into a channel, delete one
• Control who can see a meeting: change its privacy, share it with people (an email invitation or a password protected link), or take someone's access away
• Act on a live call: send the Fireflies bot into a meeting by link, pause or resume the recording, add a live action item or soundbite
• Create a bite from a time range of a meeting
• Ask AskFred new questions and follow-ups (this spends your Fireflies AI credits)
• Bring in a recording from a web address for Fireflies to transcribe
• Manage the team: set a teammate's role, add a person to a user group or take them out

Reading is free. Every change needs the Pro tier, and the ones that cannot be undone, or that reach other people, are labelled so your AI assistant asks before running them.

Before you start: the key reads exactly what its owner can read

A Fireflies API key is personal. It belongs to one person and it carries that person's access. Everyone who can use the Fireflies connector in StackJack, and every automation that uses it, reads whatever that one person can read, private meetings included.

What the key reaches depends on its owner's role:

So before you paste a key, decide whose access you are willing to share. For your own team's calls, a key from an admin is the usual choice. For a customer's Fireflies team, use a key issued by a user in that team. Fireflies has no partner or multi-workspace lane, and a key never reaches beyond the team its owner belongs to.

How StackJack authenticates to Fireflies

Fireflies gives each user an API key. You paste it into StackJack, and that is the whole credential: there is no client ID, no region and no web address to enter. Fireflies runs one shared service for every customer, so the address is fixed.

StackJack sends the key on every request and does not exchange or renew it. If the key is regenerated in Fireflies, or the person who issued it leaves, the connection stops working until you paste a new key.

Steps

1. Decide whose key to use, as described above. This is the decision people skip.
2. Open Developer settings in Fireflies. Sign in as that person, open Settings, then Developer settings (the Personal tab). The key is also available under Integrations, then Fireflies API. Fireflies' own API key guide shows where.
3. Copy the key and treat it like a password: anyone holding it can read and act on that person's Fireflies account. If it has been exposed, regenerate it in Fireflies and use the new one.
4. Check the Fireflies plan. API access is on every plan, but the budget is small below Business (see the table below). Fireflies Pro or higher is recommended.
5. Enter the key in StackJack. Open Connectors, choose Fireflies, paste the key and save.
6. Run a Test Connection. If it fails, the usual cause is a mistyped or revoked key. Fireflies refuses a bad key with a server error rather than an authorization error, so a failure with no clear message is worth checking against the key first.

What your Fireflies plan and the key owner's role decide

The request budget

Three things make the small budgets matter. StackJack checks the connection periodically, which on a Free plan uses most of the day's 50 requests, so the Free plan is not a good fit for this connector. The budget is shared with Fireflies' own MCP server and anything else using the same key. And a few actions have tighter limits of their own: adding the bot to a live meeting (3 per 20 minutes), deleting a meeting (10 per minute), sharing a meeting (60 per hour), and creating live action items or soundbites or pausing a recording (10 per hour each).

When the budget is spent, Fireflies answers with a rate limit and the time it resets. StackJack reports that time to your AI assistant so it stops instead of retrying. StackJack never retries a change on its own.

What needs a higher plan or an admin key

When Fireflies refuses because of a plan or a role, the answer names what it needs, and each tool's description says what it requires, so your AI knows it needs a different key or plan rather than different arguments.

What to know before your AI uses this connector

Reads change nothing, but they return real meeting content

Reads change nothing, but they do return your meetings: summaries, action items, full transcripts and the names and email addresses of attendees. Grant them deliberately, and remember the first section: the connection reads what the key's owner can read.

Recording links are credentials

The audio and video links expire after 24 hours, and anyone holding one can download the recording. Treat a link the way you would treat a password: do not paste it into a ticket or a shared channel. StackJack does not record these results.

A full transcript can be very long

The meeting notes, the full transcript, the recording links and the meeting analytics are separate on purpose. The transcript of a long meeting is a long answer, and a list of meetings never includes it. Ask for the notes first, and the full transcript only when you need the exact words.

Some changes reach other people

These are labelled, so your AI assistant asks first:

• Deleting a meeting or an AskFred thread is permanent. Fireflies has no undelete.
• Changing a meeting's privacy to the link setting opens the recording to anyone who has its address, and setting it to owner only locks your colleagues out of it.
• Moving meetings to a channel can widen who sees them: a channel is shared with the team (a public channel) or with its members (a private channel).
• Adding a person to a user group can give them access to the recordings an automation rule shares with that group.
• Sharing a meeting emails the people you name, who may be outside your team, and gives them access to the recording. With a password protected link (a Fireflies beta feature) the guest link is https://app.fireflies.ai/view/p/ followed by the link's identifier, and Fireflies never emails the password, so you send it yourself. Sharing again with a different password replaces the old one.
• Adding the bot to a live meeting puts a recording bot in a call that every participant can see.
• Pausing a live recording means that stretch of the meeting is never captured and cannot be recovered afterwards.
• Setting a role to admin decides who can see, share and delete every meeting in the team.
• Creating a bite with the public setting publishes the clip to anyone with its link.
• AskFred questions, live action items and live soundbites spend your Fireflies AI credits. StackJack reports the cost Fireflies returns. The credits are your Fireflies account's, not StackJack credits.

Passwords and credentials you give a tool

Three actions take a secret from you: the password of a live meeting you send the bot into, the password of a protected share link, and the download credential (a bearer token, or a username and password) Fireflies uses to fetch a recording you upload from a web address. StackJack does not record these arguments, and they travel only to Fireflies.

Uploading a recording

Asking Fireflies to transcribe a file works from a web address: Fireflies downloads the file itself, so the address must be reachable from the public internet, or protected with a download credential. StackJack never contacts that address and never uploads the file. Uploads need Fireflies Pro or higher, and an organization admin can turn them off in Fireflies.

A second route, asking Fireflies for a pre-signed upload address and confirming it afterwards, is early access at Fireflies: Fireflies has closed its allow-list, so it can refuse these two actions until your account is allow-listed. StackJack provides them, but it cannot perform the file upload between them. That step happens outside StackJack, within an hour.

Several teams

One key covers one Fireflies team. If you manage meetings in more than one Fireflies team, add one connection per team from the connector's card, name each after the team, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single team's meetings. See Several connections of one connector.

Plans and limits

Every read is available on the Free tier. Every change needs Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Fireflies tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Troubleshooting

"Fireflies rejected the API key": the key is mistyped, regenerated or revoked, or its owner's account is gone. Copy the key again under Settings, then Developer settings in Fireflies, paste it into the connector and run a Test Connection.

"This Fireflies feature needs Pro or higher" (or Business, or Enterprise): nothing is wrong with the key. The feature needs a higher Fireflies plan than the account has. See the table above.

"Fireflies accepted the API key but refused this action": the key's owner lacks the role. Team analytics, other users' meetings and team administration need a team admin, renaming a meeting needs a team admin according to Fireflies' API documentation (its MCP documentation says the meeting's owner or a team admin), and sharing, privacy changes, channel moves and deletes need the meeting's owner or an admin. Use a key from a user with that role.

"Fireflies is rate limiting this key": the plan's request budget is spent. The answer shows when it resets. On Free and Pro the reset can be hours away, so wait rather than retry, or move to a plan with a larger budget.

"Fireflies could not find that item": the ID is wrong, or the key's owner cannot see it. A private meeting, a private channel or a user outside the team all answer as not found.

A bites list is refused before it is sent: the bites list needs one of three selectors, your own bites, a meeting, or your team's bites. Provide one.

An upload is refused: an organization admin may have disabled uploads in Fireflies, the account may be on the Free plan, or, for the two early-access actions, the account may not be allow-listed.

Fireflies tools

fireflies_ · 41 tools · Free 21 · Pro 20

AskFred

Bites

Live meetings

Transcripts

Uploads

Workspace