Automation library · Content

Send daily content queue digests to Telegram from Google Drive

Started by a clock, and works across Google Drive and Telegram. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 4Service 5

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

  1. 1Every Morning at 8amSchedule triggerStarts it
  2. 2Set Digest Configuration1SetLogic
  3. 3Fetch Queue FoldersGoogle DriveService
  4. 4Analyze Queue StateCodeLogic
  5. 5Fetch Next Post DetailsGoogle DriveService
  6. 6Build Digest ContentCodeLogic
  7. 7Send Digest to TelegramTelegramService
  8. 8If Image Preview EnabledIfLogic
  9. 9Download First Image FileGoogle DriveService
  10. 10Send Image Preview to TelegramTelegramService

How it's built

Starts on
A clock
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Google Drive, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

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