Fathom

Fathom API integration with managed OAuth. Access meeting recordings, transcripts, summaries, and manage webhooks. Use this skill when users want to retrieve meeting content, search recordings, or set up webhook notifications for new meetings. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Fathom connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Fathom action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Fathom examples; they add no Fathom capability - Fathom is not an event source, a trigger cannot read Fathom data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Before installing, understand that this skill can access sensitive Fathom meeting content and can create persistent webhooks or automations if you approve them. Use read-only actions where possible, confirm every destination URL and webhook scope carefully, and revoke/delete connections, functions, triggers, or webhooks when no longer needed.