Automation library · Scheduling

Meeting transcripts into LinkedIn content with Google Docs

Started by an event in a connected app, and works across Gmail, Google Docs and Google Drive. It puts a language model behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 18 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

MediumCalls a modelRetrieval

18 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
3Services it connects to

The flow

Starts it 1Model 6Logic 4Service 7

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

  1. 1Simple MemoryMemory Buffer WindowModel
  2. 2Structured Output ParserOutput Parser StructuredModel
  3. 3Simple Memory1Memory Buffer WindowModel
  4. 4Structured Output Parser1Output Parser StructuredModel
  5. 5New Event StartedGoogle Calendar triggerStarts it
  6. 6Personal LinkedIn GeneratorAgentModel
  7. 7Company LinkedIn GeneratorAgentModel
  8. 8Filter Unwanted Event TypeFilterLogic
  9. 9Set FieldsSetLogic
  10. 10Wait till Even EndWaitLogic
  11. 11Create New FolderGoogle DriveService
  12. 12Need Transcript to be ProvidedGmailService
  13. 13Create Content DocGoogle DocsService
  14. 14Matching Post TypeSwitchLogic
  15. 15Update Content DocGoogle DocsService
  16. 16Create Transcript DocGoogle DocsService
  17. 17Update Transcript DocGoogle DocsService
  18. 18Content ResultsGmailService

How it's built

Starts on
An event in a connected app
Steps
18, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Gmail, Google Docs, Google Drive
Model
A language model, family not declared
Retrieval
Answers are drawn from documents you supply, not from the model alone

Questions

What does it need to run?

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

What starts it?

It starts on an event in a connected app.

Does it use AI?

Yes. It calls a language model. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 18 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 18 steps before you point it at anything that matters.