Description
Fireflies Meeting Transcript Import converts meetings available to a connected Fireflies account into rows in Dots’ shared Meeting Transcripts Dotabase. A GraphQL request retrieves each page’s meeting metadata, summary, action items, and speaker sentences together. The mapper composes those parts into a readable body and structured properties for date, scope, host, attendees, topics, and action-item count.
The adapter is designed for long histories. Fireflies lists meetings newest-first, so the cursor remembers both the newest observed timestamp and an inclusive older-tail boundary. If a backfill is interrupted or quota-blocked, the next run resumes from the oldest meeting already processed instead of restarting at the first page. After history is complete, the cursor switches to forward-incremental pulls.
Selling Points
- Make meeting intelligence searchable. Summaries, action items, and speaker-level transcript text become durable Dots content.
- Resume deep history efficiently. An older-tail checkpoint avoids replaying the newest pages after an interrupted backfill.
- Capture useful organizational context. Host, attendee domains, topics, date, and action-item counts become queryable properties and tags.
- Share one transcript model across providers. Fireflies rows can participate in the same searches and workflows as Fathom meetings.
- Tolerate sparse recordings. Missing sections become clearly labeled as unavailable instead of causing the meeting to be discarded.
User Story
An operations team has years of Fireflies calls and wants decisions and action items available to Dots. An owner connects Fireflies, binds the meeting resource, and starts the import. The first run walks backward through history and can resume after a quota interruption; once complete, later pulls collect new meetings while inclusive boundaries and external-id upserts prevent duplicates.
Extension Surface
This feature is configurable: binding settings choose the account, resource, target, schema strategy, mappings, cadence, and enrichment behavior. The cursor and resource behavior are implemented in packages/connectors/src/fireflies/index.ts, while packages/connectors/src/fireflies/schema-map.ts and packages/connectors/src/fireflies/map-row.ts define how Fireflies becomes the shared transcript model. The adapter’s page size is a construction option for the host, but users do not install code into this provider-specific feature.
Capabilities & Limits
Capabilities include GraphQL batch retrieval, resumable historical pagination, forward-incremental updates, structured meeting metadata, attendee and topic tags, and a composed Summary/Action Items/Transcript body. Stable transcript ids and inclusive boundaries make re-pulled edge meetings safe.
The honest limit is that the importer is one-way and depends on the meetings, fields, permissions, and quotas exposed to the connected Fireflies account. Generic speaker labels are filtered rather than treated as meaningful identities, and speaker names are not resolved into Dots user records. A content-less meeting still imports with unavailable sections clearly labeled, so presence of a row does not guarantee the provider supplied a full transcript.
Implementation Map
packages/connectors/src/fireflies/index.tspackages/connectors/src/fireflies/client.tspackages/connectors/src/fireflies/schema-map.tspackages/connectors/src/fireflies/map-row.tsapps/web/src/composition/connector-wiring.ts