Automation library · Scheduling

Convert Fathom meeting transcripts to formatted Google Docs

Started by another system calling it, and works across Google Drive. It hands the judgement calls to Gemini. 12 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: Gemini

12 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Model 3Logic 4Service 4

The steps in the order they run, from what starts it.

  1. 1Google Gemini Chat ModelLm Chat Google GeminiModel
  2. 2Structured Output ParserOutput Parser StructuredModel
  3. 3Get Fathom MeetingWebhookStarts it
  4. 4AI Meeting AnalysisChain LlmModel
  5. 5Format Key PartsCodeLogic
  6. 6Set FieldsSetLogic
  7. 7Transcript Present?IfLogic
  8. 8Create as HTMLCodeLogic
  9. 9Upload File as HTMLGoogle DriveService
  10. 10Convert to Google DocHttp RequestService
  11. 11Delete HTML FileGoogle DriveService
  12. 12Improve Page LayoutHttp RequestService

How it's built

Starts on
Another system calling it
Steps
12, with 1 branch
Size
Medium: a working afternoon
Connects to
Google Drive
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Google Drive account, and a key for Gemini. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 12 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.