Fathom Public Meeting Transcript Exporter

Export public Fathom meeting share links into clean, structured transcript records.

Turn customer-supplied public Fathom links into meeting metadata, timestamped speaker segments, and recording URLs that are ready for CRM, QA, research, or conversation-intelligence workflows.

This Actor works only with links that are publicly accessible without a Fathom account.

What does this Fathom transcript exporter do?

This Fathom scraper visits each supplied fathom.video/share/... link over HTTP and exports one meeting record per link. It reads the public share page and its displayed transcript export, then keeps transcript lines nested with their speaker and timestamp.

It is designed for exporting meetings your team is already authorized to access through a public share link. No account login, account cookie, or Fathom API key is used.

Who is it for?

• RevOps teams importing customer-call context into a CRM.
• Sales enablement teams reviewing discovery and demo conversations.
• Agencies delivering client conversation audits from client-provided links.
• Researchers organizing public interview or meeting evidence.
• QA teams checking timestamped call notes in a repeatable export format.

Why use this extractor?

Manual copy-and-paste loses structure and is slow for batches of meetings. This Actor makes public meetings consistent: one dataset item contains the source link, meeting title, timing, recording reference, and transcript segments.

It also makes access state explicit. A sign-in-gated link is returned as a skipped record instead of being retried, guessed, or accessed with credentials.

What data do I get?

Field	Description
sourceUrl	Supplied Fathom share URL
canonicalUrl	Normalized public share URL
isAccessible	Whether the link was public
accessibility	public, login_required, invalid_url, unavailable, or error
title / topic	Public meeting title and topic
startedAt	Public meeting start time when displayed
durationMinutes	Displayed duration
recordingUrl	Public recording playlist URL when displayed
transcriptSegments	Speaker, timestamp, seconds offset, and text
transcriptSegmentCount	Number of exported speech segments
error	Clear reason for a skipped link

How much does it cost to export Fathom meeting transcripts?

The Actor uses pay-per-event pricing: a small start fee plus a per-accessible-meeting export event. Inaccessible, login-required, and invalid links are not billed as exported meetings.

Apify plan discounts apply to the per-meeting event. See the Actor pricing panel for current tier prices before running a large batch.

Quick start

1. Open the Actor on Apify.
2. Paste one or more public Fathom share URLs into Public Fathom share links.
3. Set a conservative meeting limit for your first run.
4. Run the Actor.
5. Export the default dataset as JSON, CSV, or Excel.

Input

Public Fathom share links

Provide URLs in the public-share format:

https://fathom.video/share/SHARE_TOKEN

Each link becomes one output record. Query parameters are allowed and are normalized to the canonical share URL.

Maximum meetings to export

maxItems limits how many supplied URLs are processed. Start with 5 to validate links and output shape before a larger import.

Output contract

The Actor outputs one meeting per dataset item, not one row per transcript line. transcriptSegments is an array so a meeting remains a coherent CRM or analysis record.

{
  "title": "Customer discovery call",
  "isAccessible": true,
  "transcriptSegments": [
    {
      "speaker": "Alex",
      "timestamp": "2:14",
      "timestampSeconds": 134,
      "text": "We need to consolidate our reporting workflow."
    }
  ]
}

Handling inaccessible links

Fathom share settings can be changed or revoked. When a link redirects to Fathom sign-in, the Actor returns accessibility: "login_required" and does not attempt authentication.

If a URL is not a Fathom public-share URL, it returns accessibility: "invalid_url". This makes it easy to filter and fix a batch without hidden retries.

Transcript segment format

A segment is generated from the public transcript’s displayed speaker marker and following speech text. It includes a human-readable timestamp and numeric seconds offset for sorting or joining with downstream media tools.

Screen-sharing system notices are excluded from speech segments. Empty or unavailable public transcript content produces an accessible meeting record with zero segments.

CRM workflow

Use an Apify webhook or API client after a run finishes. Map title, startedAt, and transcriptSegments into your CRM’s call-note or custom-object model.

For lean CRM imports, flatten transcriptSegments in your ETL tool while retaining meetingId and sourceUrl as the join keys.

Conversation QA workflow

Filter to isAccessible = true, then review segment timestamps alongside the source recording. You can look for objection-handling phrases, required disclosures, competitor references, or follow-up commitments in your own compliant analysis workflow.

Use accessibility and error to create a remediation queue for expired client links.

Research workflow

Researchers can use public meeting links as sources while preserving a reproducible source URL and extraction time. Store the exported JSON unchanged, then create derived quotes or themes in a separate analysis table.

Do not treat a public link as permission to republish sensitive conversation content. Follow your organization’s policies and the participants’ expectations.

Integrations

• Google Sheets: export CSV from the dataset for lightweight review.
• Airtable: import meeting records and use sourceUrl as a source-of-truth field.
• HubSpot or Salesforce: create a call-note record after your approved integration validates the meeting.
• Snowflake or BigQuery: ingest JSON records for analytics and quality dashboards.
• Zapier or Make: trigger a downstream workflow from an Apify run webhook.

API usage: Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/fathom-public-meeting-transcript-exporter').call({
  startUrls: [{ url: 'https://fathom.video/share/SHARE_TOKEN' }],
  maxItems: 5,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage: Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/fathom-public-meeting-transcript-exporter').call(run_input={
    'startUrls': [{'url': 'https://fathom.video/share/SHARE_TOKEN'}],
    'maxItems': 5,
})
print(list(client.dataset(run['defaultDatasetId']).iterate_items()))

API usage: cURL

curl "https://api.apify.com/v2/acts/automation-lab~fathom-public-meeting-transcript-exporter/runs?token=$APIFY_TOKEN" \
  -H 'content-type: application/json' \
  -d '{"startUrls":[{"url":"https://fathom.video/share/SHARE_TOKEN"}],"maxItems":5}'

MCP: use this Actor from Claude

Add the Apify MCP server in Claude Code, then enable this Actor’s tool:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/fathom-public-meeting-transcript-exporter"

For Claude Desktop or another MCP client, use this server configuration:

{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=automation-lab/fathom-public-meeting-transcript-exporter"
    }
  }
}

Example prompts:

• “Export these public Fathom meeting transcripts and give me the dataset URL.”
• “Check which supplied Fathom share links are still public.”
• “Create a CSV-ready list of timestamped transcript segments from these approved meeting links.”

Privacy and legality

Only submit links you are authorized to process. This Actor intentionally does not use logins, private APIs, or cookies to bypass Fathom sharing controls. Respect contracts, participant consent, applicable privacy law, and Fathom’s terms.

A public link may still contain personal or confidential information. Apply your organization’s retention, access-control, and data-minimization policies after export.

Reliability notes

Public share pages can change. The Actor uses the page’s public server-rendered meeting payload and its associated public transcript export route, avoiding browser automation where it is not needed.

If Fathom removes a transcript from a public page, the meeting may still be returned with zero transcript segments rather than fabricated content.

Tips for clean imports

• Validate a small batch before processing a client’s full list.
• Deduplicate input links before a run.
• Preserve sourceUrl and scrapedAt for auditability.
• Filter isAccessible before triggering downstream enrichment.
• Keep transcript arrays as JSON until your destination schema is finalized.

Troubleshooting

Why did I get login_required?

The supplied link redirected to Fathom sign-in. Ask the link owner to update share access or provide a genuinely public share URL. Do not add credentials to this Actor.

Why are there zero transcript segments?

The share page may be public while no transcript is currently displayed, or Fathom may have changed the transcript format. The meeting metadata remains available as a record of what was checked.

Why is my URL invalid?

Use the exact https://fathom.video/share/... share link. App, login, and generic Fathom URLs are intentionally rejected.

FAQ

Does this Actor transcribe audio?

No. It exports transcript content displayed through a public Fathom share link. It does not download audio for transcription.

Does it work with private meetings?

No. Private and sign-in-gated meetings are reported as skipped records.

Does it use a Fathom account?

No. The Actor has no input for credentials and never uses account cookies or API keys.

Can I export recording URLs?

When a public share page displays a recording playlist URL, it is included as recordingUrl. Your downstream use must remain authorized.

Related scrapers

For adjacent automation-lab workflows, see the Google Search Scraper for source discovery and the Contact Info Scraper for approved contact-data workflows.

Support

Include a sample share URL with sensitive values redacted, the run ID, and the returned accessibility/error fields when reporting an issue. This helps distinguish a revoked link from a page-format change.

Data retention

Dataset retention is controlled by your Apify account settings. Export or delete meeting data according to your organization’s policy. The Actor does not create a separate copy outside Apify storage.

Limits

The Actor processes supplied links only. It does not search Fathom, enumerate share tokens, access accounts, or retry permission failures. Set maxItems to keep a run bounded.

Changelog

See .actor/CHANGELOG.md for user-visible releases.