Automation library · Content

YouTube to Omni-Channel Content Engine with Blog and Twitter

Started by an event in a connected app, and works across WordPress and YouTube. It hands the judgement calls to Gemini. 10 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: Gemini

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

The flow

Starts it 1Model 1Logic 5Service 3

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

  1. 1Manual TriggerManual triggerStarts it
  2. 2Edit FieldsSetLogic
  3. 3Get IDCodeLogic
  4. 4Test Mode?SwitchLogic
  5. 5Mock DataCodeLogic
  6. 6Get Video DetailsYou TubeService
  7. 7Gemini: EngineGoogle GeminiModel
  8. 8Parse ContentCodeLogic
  9. 9WP Create DraftWordpressService
  10. 10Notify SlackSlackwebService

How it's built

Starts on
An event in a connected app
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
WordPress, YouTube
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own WordPress and YouTube accounts, and a key for Gemini. 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 Gemini. Model calls are billed by the provider, not by n8n.

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.