Block 1 - Configuration
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.4
This workflow is provided as-is. Please review and test before using in production.
Blog Post Content Creation (Multi Topic with Brand Research, Google Drive, and WordPress) Description This workflow automates the full lifecycle of generating and publishing SEO optimized blog post...
n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.googledrive, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.slack, @n8n/n8n-nodes-langchain.chainllm, @n8n/n8n-nodes-langchain.lmchatopenrouter
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jonas Frewert.
Original n8n.io sourceThis workflow automates the full lifecycle of generating and publishing SEO-optimized blog posts from a list of topics. It reads topics (and optionally brands) from Google Sheets, performs brand research, generates a structured HTML article via AI, converts it into an HTML file for Google Drive, publishes a draft post on WordPress, and repeats this for every row in the sheet.
When the final topic has been processed, a single Slack message is sent to confirm completion and share links.
A Google Sheets node reads rows containing at least:
A Split In Batches node iterates through the rows one by one so each topic is processed independently.
The Configuration node maps each row’s values into:
These values are used consistently across brand research, content creation, file naming, and WordPress publishing.
A Language Model Chain node calls an OpenRouter model to gather background information about the brand and its services.
The brand context is used as input for better, on-brand content generation.
A second Language Model Chain node uses the brand research and the blog title or topic to generate a full-length, SEO-friendly blog article.
Output is clean HTML with:
<h1> at the top<h2> and <h3> headings<html> or <body> wrappersA Code node in JavaScript:
A Google Drive node uploads the generated HTML file to a specified folder.
Each topic creates its own HTML file, named after the blog title.
An HTTP Request node calls the WordPress REST API to create a post.
The post content is the generated HTML, and the title comes from the Configuration node.
By default, the post is created with status draft (can be changed to publish if desired).
After each topic is processed (Drive upload and WordPress draft), the workflow loops back to Split In Batches to process the next row.
When there are no rows left, an IF node detects that the loop has finished.
Only then is a single Slack message sent to:
Brand and Blog Title or Topic.status field (draft or publish) to match your desired workflow.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate blog content creation from topics to WordPress with AI, Google Drive & Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 18 |
| Categories | Content Creation, Multimodal AI |
| Author | Jonas Frewert |
| Published | 10 Nov 2025 |
Use the JSON export at /data/workflows/10697/10697.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Blog Post Content Creation (Multi Topic with Brand Research, Google Drive, and WordPress) Description This workflow automates the full lifecycle of generating and publishing SEO optimized blog post...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Multimodal AI use case.