Fireflies.ai helps your team transcribe, summarize, search, and analyze voice conversations.
Fireflies.ai helps your team transcribe, summarize, search, and analyze voice conversations. On Nagent, Fireflies is exposed as a fully-configurable ai meeting assistants integration that any agent can call — 21 actions, 1 trigger, and API key authentication. No code is required to wire Fireflies into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Fireflies to automate the kinds of tasks ai meeting assistants teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Fireflies also supports 1 event trigger ("Transcription Complete Trigger"), which lets your Nagent agents react to Fireflies activity in real time — for example, kicking off a downstream workflow the moment a relevant event fires.
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Fireflies into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Triggers are the entry points of agents built on Nagent — pick one to fire your agent the moment a Fireflies event happens. Webhook triggers run instantly; poll triggers check on an interval you configure. Each shows its configuration parameters and the payload your agent receives.
FIREFLIES_TRANSCRIPTION_COMPLETETriggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Payload
Type of transcript event
The transcript that was completed
Every operation an agent can call against Fireflies, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FIREFLIES_ADD_TO_LIVEThe AddToLive Action allows you to add the Fireflies.ai bot to an ongoing meeting. Note: This action requires a paid Fireflies plan to add bots to meetings.
Input parameters
Title or name of the meeting, this will be used to identify the transcribed file. If title is not provided, a default title will be set automatically
Meeting duration in minutes. Minimum of 15 and maximum of 120 minutes. Defaults to 60 minutes if param is not provided
Language code for the meeting (max 5 characters). Defaults to 'en' (English). Common codes: en, en-US, en-GB, fr, de, es, zh, ja, pt, ar. For a complete list of language codes, please view Fireflies Language Codes documentation.
Array of Attendees for expected meeting participants.
A valid http URL for the meeting link, i.e. Google Meet, Zoom, etc
Password for the meeting, if applicable.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_CONTINUE_ASK_FRED_THREADTool to continue an existing AskFred conversation thread with follow-up questions. This action CANNOT create new threads - it only works with existing thread IDs. Use when you need to maintain context from previous exchanges and ask additional questions about meeting data in the same conversation. To start a new thread, use FIREFLIES_CREATE_ASK_FRED_THREAD instead.
Input parameters
Follow-up question or query to ask in the context of the existing thread. Maximum 2000 characters.
The ID of an existing AskFred thread obtained from a previous AskFred interaction (via FIREFLIES_CREATE_ASK_FRED_THREAD or FIREFLIES_GET_ASK_FRED_THREADS). Must be a real thread ID - placeholder values like 'new' or 'latest' are not valid. To start a new conversation, use FIREFLIES_CREATE_ASK_FRED_THREAD instead.
Response format mode. Use 'markdown' for rich formatting with structure, or 'plaintext' for simple text output.
Language code for the response (e.g., 'en' for English, 'es' for Spanish). If not specified, defaults to English.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_CREATE_ASK_FRED_THREADTool to start a new AskFred conversation thread with a question about meetings. Use when you need to query meeting transcripts using natural language, either for a specific meeting or across multiple meetings with filters. Supports time-based queries and participant-focused queries.
Input parameters
Your question or query about the meeting(s). Maximum 2000 characters. Examples: 'What were the action items?', 'Who attended the meeting?', 'What were the main topics discussed?'
Filters to search across multiple meetings.
Response format - 'markdown' for rich formatting or 'plaintext' for plain text.
ID of a specific transcript/meeting to query. If provided, filters parameter is ignored. Use this for single-meeting queries. Transcript IDs are alphanumeric strings (e.g., '01JYH3WSWW2DVA72GFPQXC6ST0'). Use FIREFLIES_GET_TRANSCRIPTS to retrieve valid transcript IDs from your account.
Language code for response (e.g., 'en' for English, 'es' for Spanish, 'fr' for French).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_CREATE_BITETool to create a bite (short video or audio clip) from a transcript segment. Use when you need to extract a specific portion of a meeting recording with defined start and end times.
Input parameters
Name for the bite. Maximum 256 characters.
Summary for the bite. Maximum 500 characters.
End time of the bite in seconds. Must be greater than start_time.
Visibility settings for the bite. Array can contain 'public', 'team', or 'participants'.
Type of bite to create. Must be either 'video' or 'audio'. If not specified, defaults to 'video'.
Start time of the bite in seconds. Must be non-negative and less than end_time.
The ID of the transcript from which to create the bite.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_DELETE_TRANSCRIPT_BY_IDPermanently delete a transcript from the Fireflies account by its unique ID. This is a destructive action that cannot be undone. The transcript, along with its associated audio/video files and summaries, will be permanently removed. Rate limited to 10 requests per minute across all user tiers. Verify the target transcript via FIREFLIES_GET_TRANSCRIPTS and obtain explicit user confirmation before calling this tool.
Input parameters
The unique ID of the transcript to delete. This is a required field.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_FETCH_AI_APP_OUTPUTS2Tool to fetch AI App outputs for specific apps or transcripts. Use when you need to retrieve AI-generated results from Fireflies AI Apps for meetings.
Input parameters
Number of records to skip over for pagination.
Maximum number of apps outputs to fetch (default: 10, max: 10).
Retrieves all outputs against a specific AI App. If not provided, returns outputs for all AI Apps.
Retrieves all outputs against a specific meeting/transcript. If not provided, returns outputs for all meetings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_ASK_FRED_THREADTool to get a specific AskFred conversation thread with full history. Use when retrieving a particular AskFred thread along with all its messages and conversation details.
Input parameters
The unique identifier of the AskFred thread to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_ASK_FRED_THREADSTool to retrieve a summary of all AskFred conversation threads for the current user. Use when you need to browse or list available AskFred conversations without fetching full message history.
Input parameters
Filter threads to only those associated with a specific transcript ID. If not provided, returns all threads for the current user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_BITE_BY_IDFetches details for a specific bite by ID. Requires a Fireflies plan that supports Bites and appropriate API scope. If the bite is not found, use FIREFLIES_GET_TRANSCRIPT_BY_ID to retrieve full transcript context instead.
Input parameters
The ID of the bite to fetch.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_BITESFetches a list of bites (highlights) against input arguments. Bites are generated asynchronously after transcript completion — only call this after FIREFLIES_GET_TRANSCRIPT_BY_ID reports `status=completed`. Empty results are possible for valid meetings; use FIREFLIES_GET_TRANSCRIPT_BY_ID for full transcript context when bites are unavailable.
Input parameters
Filter to include only the user's own bites. At least one of mine, transcript_id, or my_team must be provided.
Number of bites to skip.
Maximum number of bites to fetch.
Filter to include bites from the user's team. At least one of mine, transcript_id, or my_team must be provided.
The ID of the transcript to fetch bites for. At least one of mine, transcript_id, or my_team must be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_TRANSCRIPT_BY_IDFetches details for a specific Fireflies transcript ID. Requires a paid Fireflies plan. Response is nested at data.outputs.data.transcript; fields like sentences and attendees can be null — handle gracefully. transcript.summary.action_items may be a single newline-delimited string rather than an array — split by line breaks instead of iterating as an array. Limit concurrent calls to ~3 and apply exponential backoff on 429 responses, respecting Retry-After headers.
Input parameters
The unique identifier of the transcript to fetch. This is the Fireflies transcript ID returned when listing transcripts or from the transcript_url. Only call with IDs whose transcript status is 'completed'; incomplete transcripts return partial or missing content.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_TRANSCRIPTSFetches a list of transcripts against input filters. Metadata filters (title, host_email, organizers, participants) match transcript metadata only, not spoken content. Pagination via skip/limit may trigger HTTP 429 on rapid requests; use backoff between pages.
Input parameters
Number of transcripts to skip. Use with limit for pagination; stop when returned count is less than limit.
Maximum number of transcripts to fetch. Maximum allowed value is 50.
Title of the meeting. Matches meeting metadata title only, not spoken content.
End date for filtering transcripts. Must be in ISO 8601 datetime format with timezone (e.g., '2024-08-26T23:59:59Z' or '2024-08-26T23:59:59+00:00'). Date-only formats are not accepted.
The User ID to fetch the transcripts of.
Start date for filtering transcripts. Must be in ISO 8601 datetime format with timezone (e.g., '2024-08-16T00:00:00Z' or '2024-08-16T00:00:00+00:00'). Date-only formats are not accepted. Must be earlier than to_date. Filters are evaluated in UTC — convert local date ranges to UTC to avoid silently omitting meetings.
Email address of the host of the meeting. Must be a plain email address without markup or 'mailto:' prefix. Example: 'user@example.com'.
List of organizer email addresses to filter transcripts by.
List of participant email addresses to filter transcripts by.
Whether to include AI-generated summary (action items, keywords, overview, notes, etc.) in response. Can significantly increase response size. summary.action_items may be a single formatted string rather than a list — split by newline rather than iterating as an array.
DEPRECATED: Use 'organizers' instead. Email of the organizer of the meeting.
Whether to include analytics data (sentiments, categories, speaker stats) in response. Requires Pro+ plan. If your plan doesn't support this, the request may fail with a generic error.
Whether to include audio_url field in response. Requires Pro+ plan. If your plan doesn't support this, the request may fail with a generic error.
Whether to include sentences array (transcript text with speaker/timing info) in response. Can produce very large responses - a single transcript may contain hundreds of sentences. Each sentence object contains speaker_name, text, start_time, end_time fields. Some transcripts may return null or empty sentences array.
Whether to include video_url field in response. Requires Business+ plan. If your plan doesn't support this, the request may fail with a generic error.
DEPRECATED: Use 'participants' instead. Email of a participant in the meeting.
Whether to include apps_preview (AI app outputs) in response.
Whether to include detailed user information with nested user_groups and members. When False, only basic user fields (user_id, email, name) are returned.
Whether to include detailed meeting_attendees array (display names, emails, phone numbers) in response.
Whether to include meeting_attendance array (join/leave timestamps for participants) in response.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_USER_BY_IDThe GetUser Action is designed to fetch details associated with a specific user id.
Input parameters
The User ID to the details of.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_USER_GROUPSTool to fetch a list of all user groups within the team with information about user groups including their members. Use when you need to retrieve team user groups, optionally filtering to only groups the current user belongs to with the mine parameter.
Input parameters
Filters results to return only user groups the current user belongs to when set to true. Returns all team user groups when false or omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GET_USERSFetches a list of all users within the team, including their full email addresses. Use to resolve complete email addresses from user names before passing to tools that require exact email addresses (no partial addresses or domain-only values).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_GRAPHQL_QUERYExecute an authenticated, read-only Fireflies GraphQL operation (query) and return the full raw GraphQL response (data+errors) for reliable fallback and debugging. Use when higher-level tools fail due to schema mismatches or to access raw error details.
Input parameters
GraphQL query document (read-only operations only). Must contain only 'query' operations. Mutations and subscriptions are not allowed.
GraphQL variables as a JSON object. Used to pass dynamic values to parameterized queries.
Operation name to execute when multiple operations are present in the query document.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_SET_USER_ROLETool to update a user's role within a team. Use when you need to grant or revoke admin privileges. Only team administrators can execute this action. Teams must maintain at least one admin member at all times.
Input parameters
Role assignment to set for the user. Valid options are 'admin' (grants administrative privileges) and 'user' (standard user permissions).
Unique identifier of the target user whose role will be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_UPDATE_MEETING_CHANNELTool to batch update channel assignments for 1-5 meeting transcripts. Use when you need to assign meetings to a specific channel. Requires meeting owner or team admin privileges. All-or-nothing semantics: if any transcript fails validation, none are updated.
Input parameters
The channel identifier to assign to all specified transcripts. A meeting can only belong to one channel at a time.
Array of transcript IDs to assign to the channel. Must contain between 1 and 5 transcript IDs. All specified meetings must be owned by users in your team.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_UPDATE_MEETING_PRIVACYTool to update the privacy setting of a meeting transcript. Use when you need to change meeting access permissions. Only meeting owners and team admins can update privacy settings.
Input parameters
The transcript identifier to update privacy settings for.
New privacy level setting. Available values: 'link' (anyone with link can access), 'owner' (only meeting owner), 'participants' (meeting participants only), 'teammatesandparticipants' (teammates and participants), 'teammates' (team members only).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_UPDATE_MEETING_TITLETool to update the title of a meeting transcript. Use when you need to rename a meeting. Requires admin privileges and the meeting owner must be in your team.
Input parameters
The unique identifier of the meeting transcript to update.
The new title to assign to the meeting transcript.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FIREFLIES_UPLOAD_AUDIOThe UploadAudio Action allows you to upload audio files to Fireflies.ai for transcription. Transcription is asynchronous — after submission, results may take several minutes to become available; use transcript retrieval tools to poll for completion. Note: This action requires a paid Fireflies plan to upload and transcribe audio files.
Input parameters
The url of media file to be transcribed. It MUST be a valid https string and publicly accessible to enable us download the audio / video file. Double check to see if the media file is downloadable and that the link is not a preview link before making the request. The media file must be either of these formats - mp3, mp4, wav, m4a, ogg
Title or name of the meeting, this will be used to identify the transcribed file
URL for the webhook that receives notifications when transcription completes
An array of objects containing Attendee objects. This is relevant if you have active integrations like Salesforce, Hubspot etc. Fireflies uses the attendees value to push meeting notes to your active CRM integrations where notes are added to an existing contact or a new contact is created. Each object contains - displayName, email, phoneNumber, client_reference_id
Specify whether the video should be saved or not.
Authentication details for accessing protected media files.
Specify a custom language code for your meeting, e.g. es for Spanish or de for German. For a complete list of language codes, please view Language Codes
Set to true to bypass the 50kb minimum file size validation. Useful for processing smaller audio files.
The client reference id of the attendee
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 89 agents privately built on Nagent that already use Fireflies.
Build on Nagent
Connect Fireflies to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Fireflies, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Fireflies is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Fireflies is connected, you configure its 21 actions and 1 trigger directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Fireflies steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Fireflies event fires, the agent kicks off automatically.
Every Fireflies action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Fireflies ships with 21 pre-built ai meeting assistants actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Fireflies together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Fireflies-based workflows tailored to your business.