Description
Fathom Meeting Transcript Import brings recorded meetings from a connected Fathom account into Dots’ shared Meeting Transcripts Dotabase. The adapter lists the account’s available meetings, fetches their transcript-oriented content through the managed connection proxy, describes the target schema, and maps each meeting into a row with source identity, meeting context, and a readable body.
Because it implements the common connector contract, the Fathom-specific client and mapper do not own scheduling or storage. A sync binding selects the source and target, while the engine handles the initial backfill, checkpoints, provenance-keyed upserts, retries, error records, enrichment, and later incremental pulls. The shipped web composition registers the adapter alongside the other supported providers.
Selling Points
- Turn recorded conversations into durable workspace knowledge. Meeting material becomes searchable and enrichable instead of remaining trapped in a vendor account.
- Use a shared transcript shape. Fathom rows land in the same conceptual Dotabase as other meeting providers, enabling consistent downstream workflows.
- Retain source context. Meeting timing, participants, links, and provider identity travel with the transcript.
- Refresh without multiplying meetings. Stable external ids and binding-scoped upserts preserve one Dots row per source meeting.
- Keep access credentials managed. Requests travel through the connected-account proxy instead of embedding a raw API key in the importer.
User Story
A customer research lead records interviews in Fathom and wants those conversations available to Dots search and synthesis. They connect the account, create a binding to the Meeting Transcripts Dotabase, and run a backfill. Each imported meeting becomes a structured row with a readable transcript and useful context, ready for tags, relationships, and analysis alongside the team’s other knowledge.
Extension Surface
This feature is configurable: users control the connection, source resource, target Dotabase, schema strategy, field mapping, cadence, and behavior skips through the binding. The provider implementation in packages/connectors/src/fathom/index.ts supplies the contract behavior, while packages/connectors/src/fathom/schema-map.ts and packages/connectors/src/fathom/map-row.ts define the shared transcript shape. Supporting another meeting vendor uses the framework’s plugin seam, but this Fathom workflow itself is configured rather than extended at runtime.
Capabilities & Limits
Capabilities include authenticated meeting retrieval, transcript-oriented row bodies, shared Meeting Transcripts schema mapping, stable external identity, repeatable backfill, and scheduled refresh through the generic engine. The adapter benefits from engine-level scrubbing, provenance, enrichment, and failure containment.
The importer is one-way: edits in Dots are not pushed back to Fathom. Coverage is limited to meetings and fields returned to the connected account, and provider availability, permissions, and quotas can constrain a run. Unlike the Fireflies adapter’s explicitly resumable older-tail cursor, Fathom’s exact pagination and incremental guarantees remain those implemented by its provider client rather than a universal transcript-provider promise.
Implementation Map
packages/connectors/src/fathom/index.tspackages/connectors/src/fathom/client.tspackages/connectors/src/fathom/schema-map.tspackages/connectors/src/fathom/map-row.tsapps/web/src/composition/connector-wiring.ts