Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Fireflies.ai

Meeting assistant that automatically records, transcribes, and analyzes conversations

CategoryProductivity
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Fireflies.ai with Flows360

Meeting assistant that automatically records, transcribes, and analyzes conversations

Use the Fireflies.ai connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 1 trigger.

Available actions

  • Find Meeting by ID
  • Find Recent Meeting
  • Find Meeting by Call Deatils
  • Upload Audio
  • Get User Details

Available triggers

  • New Transcription Completed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Fireflies.ai
  • Package: @activepieces/piece-fireflies-ai@0.1.6
  • Exact artifact digest: sha256:54c6c7a0b484ee1d603a3e2d99fcdf024713256f6acd777eefc800864ca7b801
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Find Meeting by ID (find-meeting-by-id), Finds a specific meeting by ID. Classification: read.
  • Find Recent Meeting (find_recent_meeting), Retrieves the latest meeting for a user. Classification: read.
  • Find Meeting by Call Deatils (find_meeting_by_query), Searches meetings based on provided parameters. Classification: read.
  • Upload Audio (upload_audio), Creates a new meeeting in Fireflies for transcription (requires a publicly accessible URL). Classification: read.
  • Get User Details (get-user-details), Retrieves profile information by ID. Classification: read.

Trigger contracts

  • New Transcription Completed, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Find Meeting by ID Yes No Finds a specific meeting by ID.
Find Recent Meeting Yes No Retrieves the latest meeting for a user.
Find Meeting by Call Deatils Yes No Searches meetings based on provided parameters.
Upload Audio Yes No Creates a new meeeting in Fireflies for transcription (requires a publicly accessible URL).
Get User Details Yes No Retrieves profile information by ID.
New Transcription Completed Yes No webhook trigger declared by the pinned package.

Supported actions

Find Meeting by ID · Read

Finds a specific meeting by ID.

find_meeting_by_id · Risk: low · Retry: safe

Inputs

  • meetingId · string · Required, The ID of the meeting to retrieve.
Find Recent Meeting · Read

Retrieves the latest meeting for a user.

find_recent_meeting · Risk: low · Retry: safe

Find Meeting by Call Deatils · Read

Searches meetings based on provided parameters.

find_meeting_by_query · Risk: low · Retry: safe

Inputs

  • title · string · Optional
  • hostEmail · string · Optional, Filter meetings by host email.
  • participantEmail · string · Optional, Filter meetings by participant email
  • date · string · Optional, Filter meetings on this date (YYYY-MM-DD).
Upload Audio · Read

Creates a new meeeting in Fireflies for transcription (requires a publicly accessible URL).

upload_audio · Risk: low · Retry: safe

Inputs

  • audioUrl · string · Required, The publicly accessible URL to your audio file (mp3, mp4, wav, m4a, ogg). Fireflies API only accepts URLs, not direct file uploads. For private files, consider using signed URLs with short expiry times.
  • title · string · Required
Get User Details · Read

Retrieves profile information by ID.

get_user_details · Risk: low · Retry: safe

Inputs

  • userId · string · Required

Triggers

New Transcription Completed · Webhook

Triggered when a new meeting is transcribed.

Inputs

  • webhookInstructions · string

Setup

Setup

  1. Add the Fireflies.ai connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-fireflies-ai@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Fireflies.ai connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-fireflies-ai@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com