Skip to main content

​
Transcript autopilot and Fathom

Transcripts are one input. They are not required to start projects. When a transcript does land, the AI Project Manager can extract commitments, route them to existing projects, create supervised new-project candidates, ask for missing owners/dates, and record decisions.

​
Current transcript lanes

The pack supports:
  • manual paste,
  • local file drop / local transcript inbox,
  • Google Drive / Gmail fallback when configured,
  • native Fathom API polling when configured.

​
Native Fathom path

Fathom is the first native transcript connector because the setup is simple for a local Hermes install:
  1. The user generates a Fathom API key.
  2. Hermes stores it through the secure credential path.
  3. The scheduler polls for completed meetings.
  4. Meetings are normalized into the same transcript event model as manual/file ingest.
  5. Duplicate transcripts are suppressed.
  6. Edited transcripts can be reprocessed when the content hash changes.
No Zapier, tunnel, webhook, or public callback URL is required for the self-install path.

​
What transcript processing does

A transcript can produce:
  • a task attached to an existing project,
  • a supervised new-project candidate,
  • an owner/date clarification,
  • a decision/rationale record,
  • a note-only receipt.
Unsafe or ambiguous work is not dispatched automatically.

​
Privacy defaults

Raw transcripts are not stored/exported by default. The pack keeps provider/source IDs, hashes, snippets where safe, extracted commitments, decisions, and receipts.

​
Other notetakers

Otter, Granola, Read.ai, Zoom, Fireflies, and other tools can use manual/file/Gmail/Drive fallback until native connectors are added. Fireflies is the likely next native connector after Fathom.