Save each Fathom meeting transcript as a new Google Docs document
When Fathom has a meeting’s content ready, this workflow creates a new Google Docs document from it, so each call’s transcript sits in your Google Drive as its own file you can search and share.
Fathom
Google Docs2 steps Setup ~5 min Used on 1.4k sites Free to import
What this workflow does
Fathom records your calls and prepares their content, but that content lives in Fathom. If you share notes with people who don't use it, or want every meeting kept in Google Drive alongside your other files, you need a copy there. This workflow makes one document per meeting.
The Fathom trigger fires when a meeting's content is ready in your account. The meeting data it receives, such as the title and the content Fathom sends, is passed on. The Google Docs step then creates a new document, and you map the meeting title and transcript into it.
Run one meeting through after import and look at the captured data, so you can confirm the transcript is part of what Fathom sends and map it into the document. Every run is logged in Task History.
Client call archive for a consultancy
Every client call recorded in Fathom gets its own Google Doc, which you can move into that client's shared folder.
Interview notes for a hiring team
Recorded candidate interviews become documents that the hiring panel can read and comment on in Google Docs.
Research calls for a product team
Customer research calls are saved as documents, so the team can search across them in Drive when planning features.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Fathom New Meeting Content ReadyRuns when Fathom has a meeting's content ready. The meeting data, including the transcript if Fathom sends it, is passed on for mapping. Connect your Fathom account on import.
- Google Docs Create Document
Creates a new Google Docs document for the meeting. Map the meeting title and transcript from Fathom into the step, then connect your Google account and check the new file after a test run.
What you need
- FlowMatticCore
- Fathom AccountAccount
- Google Docs AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Put the meeting date or attendee name in the document title, using fields from the Fathom data, so files are easy to find in Drive.
- Add a Filter after the trigger if only some meetings should be saved, for example ones whose title contains a client name.
- Add a Slack or email step after the document is created to share its link with your team, if the Google Docs step returns one.
Questions about this workflow
Does the Fathom data include the full transcript?
Check with a test meeting after import. Look at the captured trigger data to see whether the transcript is there before you map it into the document.
Where are the Google Docs documents saved?
In the Google account you connect on import. Run a test to see where the new document appears in your Drive.
Are Fathom meetings recorded before the workflow is on saved too?
No. Only meetings whose content becomes ready after you turn the workflow on start a run.
Can I save the Fathom summary instead of the transcript?
Yes, if Fathom sends it. Map the summary field into the document in place of the transcript, or put both in.
More Docs & Notes workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted