Fireflies

Your assistant can run a keyword search across what was actually said in your meetings, not just the titles and attendee lists, and you can scope it to spoken content, titles, or both, with date and participant filters on top. It then opens the matching transcripts to read the passage in context. This is the question the recording was always supposed to answer and nobody has time to answer by scrubbing through calls.

What you end up with. The meetings where the thing was actually said, with the passage quoted and the date and speaker attached.

Start with it bringing you the information and you deciding.

Never without. Read the surrounding passage, not just the hit. Transcription mishears names, numbers and negations, and a search result that looks like a commitment is often the sentence before someone walked it back.

Built on: Search Transcripts / Get Transcript by ID / Get Meeting Topics

It can pull the topics and keywords Fireflies extracted for that meeting first, which is cheap, then fetch the full transcript with its summary and action items, and list who attended with their join and leave times. One thing to expect: Fireflies sometimes returns action items as a single block of text with line breaks rather than as a list, and fields like sentences and attendees can come back empty, so an empty section means nothing was returned rather than nothing was said.

What you end up with. A written catch-up with the topics, the decisions, the action items, and who was in the room for each part.

Start with it bringing you the information and you deciding.

Never without. Never forward a summary of a call you were not on without saying it came from a transcript. The person who was there is the one who can tell you the summary read the room wrong.

Built on: Get Meeting Topics / Get Transcript by ID / Get Meeting Participants

Fireflies keeps conversation metrics at team level, and the assistant can read those alongside the user groups the team is organized into. What that answers is a question about the shape of the week: which recurring meeting has grown to three hours, which groups never overlap, where the hours are going that nobody scheduled on purpose. The same read also returns per-person figures, which is the part to leave alone.

What you end up with. A description of how meeting time is distributed across the team and its groups, with the recurring sessions that have quietly grown named.

Start with it bringing you the information and you deciding.

Never without. Never use these figures to compare one person against another. Talk time and sentiment describe a role and a meeting format, not a contribution, and the moment people learn they are measured on them the numbers stop meaning anything.

Built on: Get Meeting Analytics / Get User Groups / Get Users

Fireflies has a question-and-answer layer called AskFred, and the connector covers the whole thread: start one with a question scoped to a single meeting or to a filtered set, ask follow-ups in the same thread so the context carries, and read back a thread or list the threads you already have. Starting a thread and continuing one are separate actions, so a follow-up needs the existing thread ID rather than a new question.

What you end up with. A saved question-and-answer thread against your meetings that you can return to and add to, rather than a one-off answer.

Start with it doing the work and checking with you.

Never without. Check what the answer is drawn from before repeating it. A question filtered across many meetings can pull from a call the reader of your answer is not supposed to have access to.

Built on: Create AskFred Thread / Continue AskFred Thread / Get AskFred Thread / Get AskFred Threads

A bite is a short clip cut from a recording between a start and end time, and the assistant can create one from a transcript segment and read it back. The sequence matters: bites are generated after the transcript finishes, so it should confirm the transcript reports as completed before it goes looking. Bites also depend on your Fireflies plan supporting them, and an empty result is a real possibility for a perfectly valid meeting.

What you end up with. A short clip of the exact moment, with its ID, ready to share instead of a timestamp people will not click.

Start with it doing the work and checking with you.

Never without. Listen to the clip before sending it. A cut that starts a few seconds late turns a qualified answer into a flat commitment, and the clip travels further than the meeting ever would.

Built on: Get Transcript by ID / Create Bite / Get Bite by ID

Two routes, both covered. It can add the Fireflies bot to a meeting already in progress, or upload an audio file after the fact for transcription. Uploaded audio is transcribed asynchronously and can take several minutes, so the assistant submits it and then polls the transcript until it reports as completed rather than answering immediately.

What you end up with. A transcript of a call Fireflies was not scheduled for, searchable alongside everything else.

Start with it doing the work and checking with you.

Never without. Never add the bot or upload a recording without the consent of the people on the call. A bot joining mid-meeting is the moment recording starts, several places require everyone's agreement first, and the people on an old audio file cannot be asked afterward.

Built on: Add to Live Meeting / Upload Audio / Get Transcript by ID

It can rename a meeting transcript, and assign up to five transcripts at a time to a channel, after listing which channels exist and which ones you are a member of. Channel assignment is all or nothing per batch: if one transcript fails validation, none of them move.

What you end up with. Meetings named after what they were about and filed into the right channel, so a keyword search across your transcripts actually finds them.

Start with it doing the work and checking with you.

Never without. Never let it rename a meeting from the transcript alone without you seeing the new titles first. A title is how a colleague finds a call months later, and a confidently wrong one is worse than a generic one.

Built on: List Channels / Update Meeting Title / Update Meeting Channel

The connector can change a transcript's privacy setting, and it can delete a transcript outright. Fireflies is unusually direct about the second one: the delete is permanent, cannot be undone, and takes the audio and video files and the summaries with it, and its own guidance is to verify the target transcript first and get explicit confirmation before running it. Do it in two moves. Have it find and read back the specific transcript, confirm it is the right one, then approve that single deletion.

What you end up with. Either the meeting restricted to the people who should see it, or the transcript and its recordings gone, with a note of what was removed and when.

Start with it doing the work and checking with you.

Never without. Never approve a deletion by description rather than by transcript ID, and check whether the recording is subject to a retention or legal-hold obligation before it goes. Fireflies removes the transcript, the audio and video, and the summaries permanently, so there is nothing left to produce if someone asks for it later.

Built on: Search Transcripts / Get Transcript by ID / Update Meeting Privacy / Delete Transcript by ID