🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Fathom to Google Docs, repurpose transcripts fast

Fathom to Google Docs, repurpose transcripts fast - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Fathom to Google Docs, repurpose transcripts fast - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your best insights are trapped in meeting recordings. You know there’s good stuff in the transcript, but turning it into a post, an image idea, and a short video prompt usually turns into a “someday” task.

This Fathom Google Docs automation hits hardest for consultants who run sessions all week. Marketing leads feel it too, and educators repurposing workshops run into the same wall. You want usable content quickly, not another admin project.

This workflow pulls your latest Fathom transcript, drafts a ready-to-edit Google Doc, generates image and video prompts, and pings Slack when the video is ready. Below, you’ll see exactly what it does and what you’ll need to run it reliably.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Fathom to Google Docs, repurpose transcripts fast

The Problem: Great transcripts, zero time to repurpose them

A Fathom transcript is useful, but it’s not “content” yet. First you skim for highlights. Then you try to shape it into a post that doesn’t sound like a meeting. Then come the extras: a video concept, an image idea, and somewhere organized to store it all. Most teams end up copying text into Google Docs, rewriting sections, hunting for quotable moments, and forgetting to share the final assets. The result is inconsistent publishing and a pile of unused recordings.

The friction compounds. Here’s where it usually breaks down.

  • Finding the strongest 2-3 moments takes long enough that you push it to next week.
  • Manual copy-paste into Google Docs leads to messy formatting and missing context.
  • Video and image ideas get written in random places, so you can’t reuse them later.
  • Someone has to remember to post the video link to Slack, and honestly that’s where things get dropped.

The Solution: Turn the latest Fathom transcript into a Doc, image, and video link

This workflow starts with a simple chat request in n8n, like “Create content from my latest session.” Once triggered, it fetches your most recent Fathom transcript (focused on the last 7 days), then uses OpenAI to analyze what was said and pull out the key insights and “breakthrough” moments. From that analysis, it drafts written content and automatically creates a Google Doc you can edit, reuse, and share. In parallel, it generates an image prompt, creates a social graphic via DALL·E, uploads it to Google Drive, and assembles a clean shareable link. Finally, it sends a video generation prompt to your video provider (such as Luma or Runway), checks for the finished result, then notifies Slack with the ready video URL.

The workflow begins in chat, then branches into three content tracks: Google Docs for the written draft, DALL·E for an image asset, and a video API for a short clip. When the video is complete, Slack gets the link so you can review and publish without chasing files.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you run 3 client calls a week and want one LinkedIn post, one graphic, and one short video per call. Manually, you might spend about 30 minutes reviewing the transcript, 45 minutes drafting, 20 minutes writing prompts, and another 15 minutes tracking links and sharing updates. That’s roughly 2 hours per call, so about 6 hours a week. With this workflow, you spend maybe 5 minutes sending the chat request and skimming the finished Google Doc, while the video generates in the background (often 2-5 minutes). Your Slack message arrives with the video link when it’s ready.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Fathom to access your recorded meeting transcripts.
  • Google Docs to store editable content drafts.
  • Slack to receive the finished video link.
  • Google Drive to store and share generated images.
  • OpenAI API key (get it from the OpenAI API dashboard).
  • Video generation API access (from Luma or Runway provider settings).

Skill level: Intermediate. You’ll connect accounts, add API keys, and confirm the three subworkflows are set up once.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A chat request kicks things off. You trigger the workflow through the n8n chat interface, asking it to create content from your latest session. That message is routed into an AI “coordinator” that decides which assets to generate.

The transcript gets fetched and understood. The workflow pulls your most recent Fathom transcript (within the last 7 days) and passes it to OpenAI to extract themes, standout moments, and usable quotes. This is the part you normally do while half-reading, half-rewriting.

Three content tracks run in parallel. One track writes a structured draft and creates a Google Doc, then injects the draft so you have something clean to edit. Another track generates an image prompt, requests the image (DALL·E), converts it into a file, and uploads it to Google Drive. The third track creates a video prompt, sends it to your video provider, then retrieves the finished video result.

Slack receives the final “ready” link. Once the video URL is assembled, the workflow posts a notification in Slack so your team can review, schedule, or publish without digging through logs or tabs.

You can easily modify which transcript window you pull (like last 24 hours instead of 7 days) and where assets get posted in Slack based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Chat Trigger

This workflow starts when a user sends a chat message into n8n, which is then routed to the AI coordinator.

  1. Add the Chat Input Trigger node and keep the default options.
  2. Connect Chat Input Trigger to Content Coordinator to pass user messages into the AI orchestration layer.

Step 2: Connect Fathom Transcript Retrieval

This step ensures the workflow can pull the latest coaching session transcript from Fathom.

  1. Open Fetch Fathom Transcript and confirm the URL is https://api.fathom.ai/external/v1/meetings.
  2. Enable Send Query and verify the query parameters include include_summary=true and limit=1.
  3. Ensure Fetch Fathom Transcript is connected as a tool to Content Coordinator.

Credential Required: Connect your Fathom API credentials in Fetch Fathom Transcript (this node calls a protected API but has no credentials configured).

Step 3: Set Up the AI Coordination Layer

The AI layer coordinates transcript processing and routes to specialized sub-workflows for writing, video, and image creation.

  1. In Primary GPT Model, select the Model value gpt-4.1-mini.
  2. Credential Required: Connect your openAiApi credentials in Primary GPT Model.
  3. Set Context Buffer Context Window Length to 2 and connect it to Content Coordinator as memory.
  4. Connect Primary GPT Model as the language model for both Content Coordinator and Post Creator Agent.
  5. In Visual GPT Model, select Model gpt-4.1-mini and connect it to Video Prompt Agent and Image Prompt Agent.
  6. Credential Required: Connect your openAiApi credentials in Visual GPT Model.

AI tools like Context Buffer, Video Prompt Workflow, Image Prompt Workflow, and Transcript Writer Workflow inherit credentials from their parent AI nodes. Add credentials to Primary GPT Model and Visual GPT Model rather than the sub-nodes.

Step 4: Configure Subworkflow Outputs (Docs, Images, Video)

When the subworkflow starts, it runs three branches in parallel to generate docs, images, and video prompts.

  1. Ensure Subflow Start Trigger has inputs for post_title and post_content, as used later by Google Docs.
  2. Subflow Start Trigger outputs to both Generate Google Doc, DALL·E Image Request, and Video Creation Request in parallel.
  3. In Generate Google Doc, set Title to {{ $json.post_title }} and Folder ID to [YOUR_ID].
  4. In Inject Doc Content, set Operation to update and Document URL to {{ $json.id }}, with insert text {{ $('Subflow Start Trigger').item.json.post_content }}.
  5. In DALL·E Image Request, set URL to https://api.openai.com/v1/images/generations, Method to POST, and prompt to {{ $json.output }}.
  6. In Video Creation Request, set URL to https://api.kie.ai/api/v1/jobs/createTask and pass input.prompt as {{ $json.output }} with input.aspect_ratio landscape.

Credential Required: Connect your Google Docs/Google Drive credentials to Generate Google Doc and Inject Doc Content (these nodes call Google APIs but have no credentials configured).

Credential Required: Add API authorization headers in DALL·E Image Request, Video Creation Request, and Retrieve Video Result (these HTTP requests call protected APIs but have no credentials configured).

Step 5: Assemble Image and Video Links

These nodes convert generated assets into shareable links and prepare them for notifications.

  1. Connect DALL·E Image Request to Image to Binary File and set Operation to toBinary with Source Property data[0].b64_json.
  2. In Upload to Drive Storage, set Drive to My Drive and Folder ID to [YOUR_ID].
  3. Credential Required: Connect your googleDriveOAuth2Api credentials in Upload to Drive Storage.
  4. In Assemble Image Link, map the URL with {{ JSON.parse($json.data.resultJson).resultUrls[0] }}.
  5. Connect Video Creation Request to Retrieve Video Result, then to Assemble Video Link using {{ JSON.parse($json.data.resultJson).resultUrls[0] }}.

Step 6: Configure the Notification Output

Send the final video link to Slack once the asset is ready.

  1. Open Notify Video Ready and set Text to Your video is ready! 🎥 \n\n[Watch your coaching session video]({{ $json.videoURL }}) \n\nThis captures the key breakthrough moment from your session. The video shows the problem, the solution, and the impact - all in about 60 seconds..
  2. Set Select to channel and choose the Channel value.
  3. Credential Required: Connect your slackOAuth2Api credentials in Notify Video Ready.

⚠️ Common Pitfall: If the Slack message arrives without a link, verify that Assemble Video Link correctly extracts the URL with {{ JSON.parse($json.data.resultJson).resultUrls[0] }}.

Step 7: Test and Activate Your Workflow

Validate the full pipeline before enabling the workflow in production.

  1. Use Chat Input Trigger to send a test message like “Create content from my latest coaching session with video and image.”
  2. Confirm that Content Coordinator calls Fetch Fathom Transcript, then routes to Post Creator Agent and starts Subflow Start Trigger.
  3. Verify that Generate Google Doc creates a document and Inject Doc Content inserts the transcript-based content.
  4. Check that DALL·E Image Request → Image to Binary File → Upload to Drive Storage completes and that Assemble Image Link contains a valid URL.
  5. Confirm that Video Creation Request → Retrieve Video Result → Assemble Video Link produces a video URL and that Notify Video Ready posts it to Slack.
  6. When the run succeeds, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Docs and Google Drive credentials can expire or need specific permissions. If things break, check the n8n credential test and Google account access scopes first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Related Workflows

If you mainly need the “clean Doc” part (and not the multimodal assets), Fathom to Google Docs, meeting notes you can share is a lighter companion workflow that’s perfect for internal documentation.

For teams turning written drafts into client-ready presentations, Google Docs to Google Slides, decks built from transcripts helps you convert the finished Doc into a deck without rebuilding slides manually.

When you want recaps to land in someone’s inbox automatically (clients, stakeholders, or attendees), Google Drive to Gmail, meeting recaps sent clean fits nicely right after this workflow generates the Doc and assets.

If your bottleneck is “what do we post this week,” Google Calendar + Google Docs, LinkedIn drafts ready gives you a planning layer so transcript-driven content becomes a steady cadence.

Finally, if you also produce training materials from PDFs, PDF to Google Docs, microlearning modules ready fast pairs well because it standardizes how you turn raw source material into editable Docs.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Fathom Google Docs automation?

About 45 minutes if your accounts and subworkflows are ready.

Do I need coding skills to automate Fathom transcripts into Google Docs?

No. You’ll mostly connect accounts, paste API keys, and test a few runs.

Is n8n free to use for this Fathom Google Docs workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI usage (often a few dollars for several long transcripts) plus video generation costs (commonly $0.50-$2.00 per video).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Fathom Google Docs workflow for a different Slack channel?

Yes, and it’s a quick change. Update the Slack “Notify Video Ready” message destination, then adjust the text to include what your team cares about (Doc link, image link, and the assembled video URL). Common tweaks include posting to a client-specific channel, tagging an owner, or sending only when the transcript contains certain keywords.

Why is my Fathom connection failing in this workflow?

Usually it’s an expired token or missing permissions on the Fathom side. Reconnect the Fathom credential in n8n and rerun a test message, then confirm the transcript fetch is actually returning sessions from the last 7 days. If you have no recent recordings, the workflow can look “broken” when it’s really just empty input. Rate limits can also show up if you hammer it with lots of test runs back-to-back.

How many transcripts can this Fathom Google Docs automation handle?

On n8n Cloud Starter, you can run about 2,500 executions per month, and higher plans handle more. If you self-host, there’s no execution cap (it depends on your server and API limits). Practically, most teams run this a few times a day, and the bigger constraint is OpenAI token usage plus the video provider queue time. The workflow’s transcript window is the most recent 7 days, so it’s optimized for “latest session” use, not bulk backfills.

Is this Fathom Google Docs automation better than using Zapier or Make?

Often, yes, because this isn’t a simple “send transcript to Doc” zap. You’ve got branching logic, multiple AI calls, file handling (image to binary to Drive), plus polling a video API result, and n8n is built for that kind of flow without turning into a fragile chain. The other advantage is control: self-hosting gives you unlimited executions, which matters once you run it after every meeting. Zapier or Make can still work if you strip it down to one output (just the Doc), but the multimodal parts get expensive and fiddly. If you want a quick recommendation based on your volume and tools, Talk to an automation expert.

Once this is running, every recorded session can turn into a draft, a visual, and a video concept without you babysitting the process. Set it up, run it after calls, and keep the momentum.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.