Resources · Make integration

Fathom Make integrationAutomate Fathom with Make.

What happens to a Fathom recording once it is saved? The Fathom Make integration gives you 8 modules, including 1 trigger and 4 searches, to pull recordings, summaries and transcripts into other tools. This guide walks you from the connection to a first working scenario.

Try the Fathom integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fathom Make integration do for you?

The Fathom Make integration links your Fathom account to Make so that recordings, summaries and transcripts can travel to your other apps without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each one being a single brick such as a trigger, an action or a search.

A recap that reaches the right place. Watch New Recordings spots each new recording, Get a Summary fetches its summary, and a module from another app stores it, for instance a row in a base described on our Airtable Make integration page.

A searchable archive of full text. When the summary is too short for your needs, Get a Transcript returns the whole text of a recording, ready to be filed in a document tool or a knowledge base.

A view of who records what. List Teams and List Team Members return the structure of your Fathom workspace, useful when a sales lead wants recordings routed by team rather than by person.

The Fathom documentation on Make gives no numeric limit and no official description for these modules, so this page sticks to what their names and types tell you. Anything the 8 modules do not cover goes through Make an API Call, with the same connection. The same apps often exist as n8n nodes too; the n8n vs Make comparison sets out how the two tools differ, and our Make training covers scenario building from the ground up.

Connect

How do you connect your Fathom account to Make?

  1. 01

    Add a Fathom module

    You need an active Fathom account first, since the Fathom documentation requires one. In your scenario, add any Fathom module, then click Create a connection. A connection is your Fathom account linked to Make once and reused by every Fathom module.

  2. 02

    Name the connection

    This step is optional, yet a clear name such as Fathom sales team saves confusion later, when several people or several Fathom accounts share the same Make organization and the list of connections grows.

  3. 03

    Authorize and save

    Make opens the Fathom authorization page, or asks for the key Fathom gives you. Approve the access, then click Save. From now on, every Fathom module in any of your scenarios can pick this connection from its list.

First scenario

Your first scenario: send every new Fathom summary onward

GoalWhen a new recording appears in Fathom, Make fetches its summary so the next module can pass it on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place your first module.

  2. 02

    Add Watch New Recordings

    Search for Fathom, choose Watch New Recordings and pick the connection you created. If none exists yet, click Create a connection here and follow the three steps above.

  3. 03

    Chain Get a Summary

    Click the + on the right of the trigger, pick Get a Summary, and map the recording that the trigger returned so Make knows which summary to fetch.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open each module to read the bundles it received, a bundle being one item passed along, here one recording.

  5. 05

    Schedule and switch on

    On the first module, check the schedule: every 15 minutes by default, with 15 minutes as the minimum on the Free plan. Then switch the scenario on so it keeps running without you.

Triggers

What starts a Fathom scenario

1 module starts a scenario when something happens in Fathom. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Fathom as soon as it happens.

Fathom1Watch New Recordings

Watch New Recordings

triggerIn the docs only

Watch New Recordings hands your scenario each recording that is new in Fathom since the last check, so nothing recorded slips past the rest of your flow. It is the only Fathom trigger, which makes it the natural first module of almost any Fathom scenario.

How it fires
it is a scheduled trigger, so Make checks Fathom on the scenario's schedule, every 15 minutes by default, and the module carries a clock badge.
When to use it
whenever something should happen after a recording exists, such as filing its summary or alerting a colleague.
Watch out
a recording reaches the scenario at the next check, never the moment it is saved, so do not promise instant alerts.
Modules

What else the Fathom modules can do

Fathom gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Fathom1

Get a Summary

ActionIn the docs only

Get a Summary brings back the summary of one Fathom recording, which gives you a short text you can drop into a message, a CRM note or a spreadsheet cell.

When to use it
right after Watch New Recordings, when a recap is enough and the full text would be noise.
Watch out
the module needs to know which recording to read, so map it from the trigger or from a list module placed before it.
Fathom2

Get a Transcript

ActionIn the docs only

With Get a Transcript you receive the complete text of a recording rather than a digest, the material you want for an archive or a search in your documents.

When to use it
pick it over Get a Summary when someone must be able to check exact wording later, for instance in a shared knowledge base.
Watch out
like Get a Summary, it acts on one recording at a time, so point it at the right one.
Fathom3

List Recordings

SearchIn the docs only

List Recordings returns the recordings of your Fathom account as separate bundles, which lets you process a batch instead of waiting for new ones to arrive.

When to use it
when you connect Fathom for the first time and want to push existing recordings into another tool once.
Watch out
a search can return zero, one or many bundles, and every following module then runs once per bundle.
Fathom4

List Recordings (Advanced)

SearchIn the docs only

This second listing module also returns recordings, and its name suggests more settings than the plain List Recordings; the Fathom documentation on Make does not spell out the difference.

When to use it
when the plain version does not let you narrow the list the way you need, open this one and compare the options Make shows.
Watch out
test with Run once before chaining actions, to see how many bundles come back.
Fathom5

List Team Members

SearchIn the docs only

List Team Members gives you the people of your Fathom workspace as bundles, handy to match a recording with the right colleague in another app.

When to use it
when a sales manager wants each recap sent to the person concerned, or when you keep a directory in sync.
Watch out
each member becomes its own bundle, so any module placed after it runs once per person.
Fathom6

List Teams

SearchIn the docs only

List Teams returns the teams defined in Fathom, one bundle each, which gives your scenario a way to group work by team rather than by individual.

When to use it
alongside List Team Members, when routing depends on the team, for example support recordings kept apart from sales.
Watch out
an empty result means no bundle, and the modules after it simply do not run.
Fathom7

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Fathom API from your scenario, using the connection you already have, so a missing module does not block you.

When to use it
only after checking that none of the seven other Fathom modules does the job.
Watch out
you write the request yourself, so keep the Fathom API reference open and test with Run once.
Need help

Need help automating Fathom with Make?

A person reads every message.

FAQ

Questions about Fathom and Make

01Is the Fathom Make integration free?
Yes, on the Make side. Fathom is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month, one operation being one module run on one item. The Fathom account itself is a separate matter, covered by Fathom pricing.
02What does Make need to connect a Fathom account?
An active Fathom account, which the Fathom documentation on Make lists as the only prerequisite. After that, the flow is the usual Make one: add a Fathom module, click Create a connection, give it a name if you like, authorize Make on the Fathom page or paste the key Fathom provides, and click Save. The connection is then shared by every Fathom module in your scenarios, so this step happens once and not per module.
03Does the Fathom trigger in Make react in real time?
No. Watch New Recordings is a scheduled trigger: Make asks Fathom for new recordings on the schedule of the scenario, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed, while paid plans can go down to 1 minute. A recording therefore shows up in your scenario at the next check, not the instant it is saved. The clock badge on the module in the editor is the visual reminder of this behavior.
04What if a Fathom module is missing in Make?
Use Make an API Call. This module reaches any endpoint of the Fathom API with the same connection as the other modules, so you can cover an operation the 8 listed modules do not offer. You write the request yourself, which asks for a look at the Fathom API reference. The Fathom documentation on Make gives no numeric limit, so if a result looks incomplete, run the scenario once and read the bundles each module received before changing anything.
05Should Fathom be automated with Make or with n8n?
It depends on the tool your automations already live in. On Make, Fathom comes with 8 modules: 1 scheduled trigger, 3 actions, including Make an API Call, and 4 searches, all shown on this page. The same apps often have an n8n node as well, so check whether one exists for Fathom before choosing. Neither tool is ranked here: the n8n vs Make comparison on our site lays out the differences, and the right choice is the one that fits the rest of your scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations