Fathom integration

Fathom meeting notetaker automation

14 operationsMeetings

Fathom is an AI notetaker that records, transcribes, and summarizes your video calls. The NoClick Fathom node reads that data through the Fathom API, so a workflow can pull a recording's summary or full transcript, list recent meetings by type, and surface the ones that carry action items, CRM matches, or written summaries. It can also read your teams and team members, and register or remove webhooks so meeting events flow straight into your automations. Point it at your call history and every meeting becomes something a workflow can act on instead of a recording you have to reopen.

What you can automate with Fathom

Fathom operations

Triggers1

Meetings7

Recordings2

Teams2

Webhooks2

Templates using Fathom

Meeting Follow-up Agent

Turns every recorded call into a follow-up email drafted in Gmail and a HubSpot note, carrying only the next steps people actually agreed to on the call. The follow-up email decides whether a call goes anywhere, and it is usually written from memory two days late. This agent reads the recording's summary and full transcript the moment it lands, drafts the follow-up in Gmail in your voice, and logs the CRM note your rules ask for. It writes down only what was actually spoken on the call, so nobody ends up agreeing to things on your behalf. ## What people use it for - **Follow-ups go out same day** - The draft is waiting in Gmail before the rep has finished tidying their notes. A call that ends at 17:00 gets followed up that evening instead of on Thursday. - **Next steps with owners** - Each action carries the person who committed to it and the date they said out loud. Where nothing was agreed the email says so, and that is what makes a recap safe to send. - **CRM notes that get read** - What was discussed, what was agreed, and what is still open, written to HubSpot on every call. The next person to open that record does not have to watch a 40 minute recording. - **Customers in their own language** - The recap is written in the language the customer actually spoke, so the person who has to forward it to their finance director is not translating it first. ## Before you fork **What do I need to connect?** Your Fathom account for the recordings, summaries, and transcripts, a Gmail credential that can create drafts, and a HubSpot credential that can search contacts and write notes. Then you describe how your follow-ups read and what a CRM note should contain. The only email tool wired in creates drafts, so every follow-up waits in your drafts folder for a person to send. **How do I know it will not promise something we never agreed?** Next steps are taken from the transcript rather than the summary, and each one has to carry the person who said it and the date they gave. Anything floated but not settled, an improvised discount for example, is kept out of the commitments and flagged with a needs a human line at the top of the draft. Prices, dates, and scope that nobody spoke on the call never appear in the email. **Does it run on every recording?** It starts on every recording Fathom finishes and then decides what to do. Calls where everyone is a colleague get the CRM note your rules ask for and no email, so internal reviews never turn into customer follow-ups. Cost is one run per recorded meeting, which tracks how much your team actually sells rather than how many seats you have.

122705 nodes

Questions

Yes. The Fathom node has operations to get a recording's summary and its full transcript, and to list meetings that already carry written summaries. You can hand either one to an AI step or write it straight into another tool.

Yes. The On New Meeting trigger fires when Fathom finishes a call, so the workflow runs on its own with the new meeting as its input. From there you can fetch its summary, read the transcript, or route it based on meeting type.

Add your Fathom API key when you configure the node. The node authenticates with that key on every call, and the same credential covers listing meetings, reading transcripts, and managing webhooks.

It can list the meetings that Fathom has already matched to a CRM contact or account, so a workflow can route those calls or update the linked record. Pair it with a CRM node to write the summary or action items back.

Yes. There is a dedicated operation to list meetings that have action items, so a workflow can collect them across recent calls and create tasks or reminders. You can also read the meeting types and team members to decide who each item belongs to.