Fathom Trigger
AI-generatedOverview
This node acts as a webhook trigger for Fathom, a meeting content platform. It listens for specific events, such as when new meeting content (recording, transcript, or summary) is ready, and triggers workflows in n8n accordingly. This is useful for automating processes that depend on meeting content availability, like notifying teams, archiving data, or further processing meeting transcripts.
Use Case Examples
- Trigger a workflow when a new meeting recording is available to automatically upload it to a cloud storage service.
- Start a transcription analysis workflow when a new meeting transcript is ready.
- Send notifications to a chat application when a meeting summary is generated.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Fathom event to listen for, such as new meeting content being ready. |
| Webhook Secret | A secret key used to verify the authenticity of incoming webhook requests from Fathom. This must be manually registered in the Fathom UI and matched in the node configuration. |
Output
JSON
- `` - The JSON payload received from the Fathom webhook, containing event data such as meeting recordings, transcripts, or summaries.
Dependencies
- Requires an API key credential for Fathom API authentication.
Troubleshooting
- If the webhook secret is missing or incorrect, the node will respond with 'Unauthorized: Missing signature' or 'Unauthorized: Invalid signature'. Ensure the webhook secret matches exactly with the one configured in Fathom UI.
- The webhook must be manually registered in the Fathom UI under Settings → Integrations → API → Webhook Secret. Failure to do so will prevent the node from receiving events.
- Check that the incoming webhook requests include the 'webhook-signature' header; otherwise, the node will reject the request.
Links
- Fathom Webhooks Documentation - Official documentation on setting up and using webhooks with Fathom.