Fathom

**Judgment** A strong, well-documented skill for integrating Fathom meeting data into assistants and automations. It is best suited for environments that already trust Maton as a proxy and can safely handle sensitive meeting content (transcripts, summaries, and action items). **What it does well** - Makes Fathom OAuth easy by centralizing connection management at Maton (no custom OAuth implementation needed). - Covers key Fathom functionality: listing meetings, getting summaries and transcripts, listing teams/team members, and managing webhooks. - Documentation is clear with concrete Python/JavaScript examples, parameter explanations, and error-handling notes. **Key risks / limitations** - **External dependencies:** Availability and latency depend on both Maton and Fathom. Any outage or change on either side affects this skill. - **Sensitive data handling:** Transcripts and summaries can contain PII, confidential business information, and CRM-related data; API keys and webhook endpoints must be stored and transmitted securely. - **OAuth connection requirement:** Each user needs an active Fathom OAuth connection; missing or invalid connections result in 4xx errors that calling code must handle. - **Scope limited to Fathom:** For other third-party integrations, a different skill (api-gateway) is required. **Recommended scenarios** - Assistants that answer questions about previous calls, generate follow-ups or summaries, or surface action items from Fathom recordings. - Workflow automations where new Fathom meetings should automatically sync into CRMs, project management tools, or data warehouses via webhooks. - Internal analytics or reporting tools that need structured access to meetings, teams, and team members from Fathom. - Any system that wants to add Fathom-based call history and context into broader conversation intelligence or knowledge-management solutions.