A 86-step content & publishing automation, triggered by sub-workflow, connecting HTTP / REST API, Google Gemini, Google Sheets, AWS S3, WordPress, Google Drive and more, with built-in AI reasoning.
In plain terms: this writes and publishes content for you. It uses AI to understand and generate content, so it handles judgement-style work, not just moving data. It runs on demand, creates the piece, and pushes it to Google Gemini, Google Sheets, AWS S3, WordPress — replacing hours of manual writing and posting.
86
Nodes
7
Integrations
103
Connections
Sub-workflow
Trigger
🚀 Deploy this workflow
Deploy this automation in minutes
Log in and we'll walk you through every key step by step, then deploy it for you.
The real node graph exported from n8n — triggers (green), AI nodes (violet), services and logic — laid out as they run.
⚙️ How it works
URL_search· httpRequestTool
Pro_search· httpRequestTool
internal_links· toolWorkflow
url_search· httpRequestTool
ranked_keywords· toolWorkflow
related_keywords· toolWorkflow
keyword_ideas· toolWorkflow
When Executed by Another Workflow· executeWorkflowTrigger
url_Search· httpRequestTool
Think· toolThink
2.5 Flash· lmChatGoogleGemini
2.5 Pro· lmChatGoogleGemini
2.5 pro· lmChatGoogleGemini
ai_mode· toolWorkflow
💼 Business analysis
🎯
Business use case
An end-to-end content production line — research, generation, formatting and publishing (HTTP / REST API, Google Gemini, Google Sheets, AWS S3, WordPress, Google Drive and more) — that lets one operator ship the output of a whole content team. It turns a keyword or brief into a published, SEO-ready asset.
📈
Market need
Content is the #1 demand-gen channel and the most time-expensive. Automating the pipeline collapses cost-per-article from hours to minutes.
💰
Market value
Content pipelines replace retainers of $1,500–$8,000/mo. Sold as a service or template, they carry strong recurring value tied to output volume.