The flow
Starts it 1Model 1Logic 9Service 7
The steps in the order they run, from what starts it.
- 1Google Drive TriggerGoogle Drive triggerStarts it
- 2CONFIG - Edit Settings HereSetLogic
- 3HTTP Request (Export HTML)Http RequestService
- 4Code (Extract Body)CodeLogic
- 5Code (Prepare Metadata)CodeLogic
- 6HTTP Request (WP - Find Post by Slug)Http RequestService
- 7Merge (Meta + FindResult)MergeLogic
- 8IF (Found Post?)IfLogic
- 9HTTP Request - WP Update PostHttp RequestService
- 10HTTP Request: WP - Create PostHttp RequestService
- 11SET - SEO InputSetLogic
- 12GEMINI - SEO JSONGoogle GeminiModel
- 13MERGE - Attach postIdMergeLogic
- 14CODE - Parse & QA SEOCodeLogic
- 15CODE - Build WP PayloadCodeLogic
- 16HTTP - WP Update SEO (RankMath)Http RequestService
- 17HTTP - WP Get Post (Verify)Http RequestService
- 18Google Drive - Move to PublishedGoogle DriveService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, 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 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. 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 itNothing 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.