Integrations · ProductivityConnect Fireflies to Well
Index Fireflies meeting recording, transcript, and speaker so questions about audit attachment and indexed record answer themselves in conversation.
What Well pulls from Fireflies
Fireflies feeds meeting recording, transcript, speaker into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Fireflies’s access.
| From Fireflies | In Well | Relation | |
|---|---|---|---|
| Meeting recording | Audit attachment | Preserves as | |
| Transcript | Indexed record | Becomes | |
| Speaker | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Fireflies → Well
What Well does with your Fireflies connection
Connect
Connect Fireflies over OAuth (MCP DCR): Well registers a client through Fireflies's OAuth Dynamic Client Registration and you approve on Fireflies's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings meeting recording, transcript, and speaker in from Fireflies on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Fireflies entity into audit attachment, indexed record, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Fireflies lands in the workspace as audit attachment, indexed record, and team member you can search, chart, and automate.
Questions Fireflies unlocks
Ask in plain language. Well answers from your connected Fireflies connection, resolved against the rest of your stack.
Ask anything about your Fireflies connection
Ask about your Fireflies connection…
Connect Fireflies in three steps
- 01
Authorise Fireflies via MCP
From Well's Connections panel, search for Fireflies and click Connect. Well discovers Fireflies's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Fireflies's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapi.fireflies.ai/mcp
- 02
Map your entities
Well's MCP client discovers meeting recording, transcript, and speaker from Fireflies that Fireflies's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Fireflies records. Because Fireflies ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Fireflies records happens in the background.
How Fireflies stays secure with Well
Well connects to Fireflies's MCP server (api.fireflies.ai/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Fireflies secret. Tokens are scoped to the meeting recording, transcript, and speaker Fireflies exposes and refreshed server-side. Reads only, Well cannot modify or delete Fireflies records.
- granted
Read Fireflies records
Resources the Fireflies MCP server exposes, scoped by your OAuth approval.
- granted
Resolve meeting recording, transcript, and speaker across your stack
Match identifiers in Fireflies against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Fireflies records
Not granted; Fireflies is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Fireflies passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Fireflies and Well
From Well, open Connections, find Fireflies, and click Connect. Well discovers the OAuth metadata at api.fireflies.ai/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Fireflies's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in meeting recording, transcript, and speaker from Fireflies and reshapes each entity into your workspace: meeting recording becomes audit attachment; transcript becomes indexed record. Every record arrives with the source identifier preserved, so Fireflies stays the source of truth while Well lets you query the data alongside the rest of your stack.
Fireflies items linked to engineering issues, deploys, or revenue commitments inherit those joins in your workspace. The product roadmap question "what's blocking enterprise rollout this quarter" returns the Fireflies items, the engineering work they depend on, and the customers waiting on the outcome, all in one answer.
Well watches for updates to meeting recordings and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right audit attachment. Edits flow in incrementally; nothing is duplicated, and the Fireflies source identifier is retained on every revision.
Well combines live Fireflies events with periodic reconciliation reads of meeting recording, transcript, and speaker. New rows appear within seconds when Fireflies pushes them; periodic reads catch anything a push missed. The first connect backfills history from Fireflies in the background.
Open Connections > Fireflies in Well and click Disconnect. Well calls Fireflies's token revocation endpoint and stops calling Fireflies immediately on its side; provider-side propagation to Fireflies's admin panel varies by provider. The meeting recording, transcript, and speaker Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Fireflies records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Fireflies
More in Productivity
Asana
Connect Asana to Well to sync tasks, projects, and team workflows.
Atlassian
Connect Atlassian to Well to sync tasks, projects, and team workflows.
Circleback
Connect Circleback to Well to sync tasks, projects, and team workflows.
ClickUp
Connect ClickUp to Well to sync tasks, projects, and team workflows.
Popular cross-category
Ready to connect Fireflies?
Connect once. Every meeting recording, transcript, speaker from Fireflies becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.