Fathom Cost Tuning

Prerequisites

• An aggregate usage/cost baseline, budget owner, recording/consent policy, quality/delivery SLO, and synthetic evaluation fixture.

Instructions

1. Measure aggregate meeting volume, processing, sync/follow-up behavior, errors, and cost by approved scope.
2. Change one reversible setting and compare against the baseline and consent/delivery safeguards.
3. Retain the change only after owner approval; restore the prior setting on regression.

Output

• A measured cost decision with owner, data/consent/delivery guardrails, and rollback threshold.

Examples

Evaluate a development workflow with synthetic meeting metadata, reduce duplicate processing or unnecessary integration calls, and compare aggregate cost/latency/error metrics. Revert on quality, consent, or CRM-sync regression; do not disable audit, retention, or access controls to save cost.

Overview

Fathom pricing scales with per-seat licensing for team features, with primary cost drivers being transcript storage volume and recording hours consumed. Every meeting generates a transcript and AI summary that persist in storage. For organizations running dozens of meetings daily, unchecked transcript accumulation and redundant API polling for meeting data create unnecessary spend. Optimizing retrieval patterns and storage lifecycle directly reduces both API costs and plan overhead.

Cost Breakdown

API Call Reduction

class FathomTranscriptCache {
  private cache = new Map<string, { transcript: string; summary: string }>();

  async getTranscript(meetingId: string, apiFn: () => Promise<any>): Promise<any> {
    // Transcripts are immutable after generation — cache permanently
    if (this.cache.has(meetingId)) return this.cache.get(meetingId);
    const result = await apiFn();
    this.cache.set(meetingId, result);
    return result;
  }

  async listMeetings(params: { include_summary: boolean }): Promise<any[]> {
    // Always use include_summary=true to avoid 

Fathom Debug Bundle

Prerequisites

• An issue owner, affected environment, approved incident/support destination, and strict redaction policy for meeting content and credentials.

Instructions

1. Collect only correlation IDs, environment, versions, configuration state, status classes, and aggregate timing.
2. Review the bundle for recordings, transcripts, participant data, CRM records, tokens, and private links before distribution.
3. Reproduce with a synthetic meeting/test account and retain the minimum approved evidence.

Output

• A minimal redacted diagnostic bundle with owner, scope, evidence, and safe escalation/recovery path.

Error Handling

Examples

For a CRM-sync failure, collect opaque meeting/action IDs, environment, mapping version, status class, and timestamp, then reproduce with a synthetic record. Do not attach recordings, transcript text, contact details, or tokens to the case.

Overview

Collect Fathom API connectivity status, meeting recording metadata, transcript availability, and authentication state into a single diagnostic archive. This bundle helps troubleshoot missing transcripts, failed meeting syncs, webhook delivery issues, and API authentication problems. Attach the output to Fathom support tickets so engineers can diagnose integration failures without back-and-forth.

Debug Collection Script

#!/bin/bash
set -euo pipefail
BUNDLE="debug-fathom-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"

# Environment check
echo "=== Fathom Debug Bundle ===" | tee "$BUNDLE/summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE/summary.txt"
echo "FATHOM_API_KEY: ${FATHOM_API_KEY:+[SET]}" >> "$BUNDLE/summary.txt"

# API connectivity
HTTP=$(curl -s -o /dev/null -w "%{http_code}" \
  -H "X-Api-Key: ${FATHOM_API_KEY}" \
  https://api.fathom.ai/external/v1/meetings?limit=1 2>/dev/null || echo "000")
echo "API Status: HTTP $HTTP" >> "$BUNDLE/summary.txt"

# Recent meetings (last 5)
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/meetings?limit=5" \
  > "$BUNDLE/recent-meetings.json" 2>&1 || true

# Check transcript availability for latest meeting
MEETING_ID=$(curl -s -H "X-Api-Key: ${FA

Fathom Deploy Integration

Prerequisites

• A versioned deployment/configuration, approved tenant/data/consent policy, scoped secret reference, owner, and rollback plan.

Instructions

1. Deploy to development/staging with synthetic meeting data and validate access, mapping, callbacks, redacted telemetry, and recovery.
2. Promote only through an approved production canary with named observer.
3. Roll back or pause on consent, access, data, delivery, or reliability regression.

Output

• A staged deployment receipt with owner approval, synthetic validation, canary evidence, and rollback reference.

Examples

Deploy a versioned CRM-sync integration to staging with scoped credentials, test a synthetic meeting/action, and verify mappings and alerts. Promote an approved canary only; restore the prior configuration if unexpected access, follow-up, or data behavior occurs.

Overview

Deploy a containerized Fathom AI meeting integration service with Docker. This skill covers building a production image that connects to the Fathom API for processing meeting transcripts, summaries, and action items. Includes environment configuration for webhook handling, health checks that verify Fathom API connectivity and transcript retrieval, and rolling update strategies to maintain continuous meeting data processing without losing webhook events.

Docker Configuration

FROM node:20-slim AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY tsconfig.json ./
COPY src/ ./src/
RUN npm run build

FROM node:20-slim
RUN addgroup --system app && adduser --system --ingroup app app
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package*.json ./
USER app
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
  CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]

Environment Variables

export FATHOM_API_KEY="fthm_live_xxxxxxxxxxxx"
export FATHOM_BASE_URL="https://api.fathom.video/v1"
export FATHOM_WEBHOOK_SECRET="whsec_xxxxxxxxxxxx"
export LOG_LEVEL="info"
export PORT="3000"
export NODE_ENV="production"

Health Check Endpoint

import express from 'express';

const app = express();

app.get('/health', async (req, res) => {
  try {
    const response = await fetch(`${process.env.FATHOM_BASE_URL}/meetings`, {
      headers: { 'Authorization': `Bearer ${process.env.FATHOM_API_KEY}` },
    });
    if (!response.ok) throw new Error(`Fathom API returned ${response.status}`);
    res.json({ status: 'healthy', service: 'fathom-integration', timestamp: new Date().toISOString() });
  } ca

Fathom Hello World

Examples

Create a development-only synthetic meeting/test account, verify the basic Fathom workflow and any resulting summary/action state, then remove or expire the fixture under policy. Record only environment and opaque result IDs; never use a customer recording, transcript, participant identity, or production CRM contact as a tutorial example.

Overview

First API calls against Fathom: list meetings, get a transcript, retrieve AI-generated summaries and action items.

Prerequisites

• Completed fathom-install-auth setup
• At least one recorded meeting in Fathom

Instructions

Step 1: List Meetings

curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/meetings?limit=5" \
  | jq '.meetings[] | {id, title, created_at, duration_seconds}'

Step 2: Get Meeting Transcript

RECORDING_ID="your-recording-id"

curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/recordings/${RECORDING_ID}/transcript" \
  | jq '.segments[] | {speaker, text, start_time}'

Step 3: Get AI Summary and Action Items

# Get meeting with summary included
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/meetings?include_summary=true&limit=1" \
  | jq '.meetings[0] | {title, summary, action_items}'

Step 4: Filter Meetings by Date

# Meetings from the last 7 days
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/meetings?created_after=2026-03-15T00:00:00Z&limit=20" \
  | jq '.meetings | length'

Output

• List of meetings with IDs and metadata
• Full transcript with speaker labels and timestamps
• AI-generated summary and action items

Error Handling

Resources

• Fathom API Reference
• Get Transcript

Next Steps

Proceed to fathom-local-dev-loop