Generate and Publish SEO-Optimized Blog Posts to WordPress
BlogBlitz is a powerful n8n workflow that automates the creation and publishing of SEO-optimized blog posts to WordPress, saving you hours of manual content creation. Triggered on a schedule or via Telegram, it generates high-quality, 1,500–2,500-word articles complete with titles, slugs, meta descriptions, images, and more.
🎯 Who is this for?
- Bloggers who want fresh, consistent content.
- Content marketers aiming for SEO efficiency.
- WordPress site owners looking to automate blog publishing without sacrificing quality.
🚨 Problem Solved
Manually creating engaging, SEO-friendly content is time-consuming and requires writing expertise. BlogBlitz solves this by:
- Automating ideation, writing, formatting, and publishing.
- Generating images and SEO elements.
- Keeping your blog active and visible to search engines.
⚙️ What This Workflow Does
| Feature | Description |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Triggers | - Runs every 3 hours via Schedule Trigger<br>- Or on-demand via Telegram command: /generate |
| Generates Content | Uses OpenRouter to: <br>- Select a category (Technology, AI, etc.)<br>- Create a title, slug, focus keyphrase, and meta description |
| Writes Articles | OpenAI generates 1,500–2,500-word articles:<br>- SEO-optimized<br>- Structured with headings<br>- Includes CTA |
| Adds Visuals | Generates realistic featured images with OpenAI and uploads them to WordPress |
| SEO Features | Generates:<br>- Optimized slug<br>- Focus keyphrase<br>- Meta description |
| Publishes | Posts directly to WordPress:<br>- With correct category<br>- Featured image<br>- Author ID |
| Notifies | Sends publish alerts via Discord webhook and Telegram message |
🚀 Setup Instructions
✅ Requirements
- Self-hosted or cloud n8n instance
- Stable internet connection
🔐 Credentials Needed
- WordPress API (
wp-json/wp/v2) - OpenAI API (text + image generation)
- OpenRouter API (category & title generation)
- Telegram Bot API
- Discord Webhook
🔧 WordPress Configuration
-
Set up post categories:
- Technology
[ID:3] - AI
[ID:4] - Tech Fact
[ID:7] - Tech History
[ID:8] - Tech Tips
[ID:9]
- Technology
-
Use admin user ID for publishing (default:
1)
🧩 Node Setup
- Telegram Trigger — Initiates workflow with
/generate - Schedule Trigger — Runs workflow every 3 hours
- Edit Fields Node — Centralizes variable setup (e.g., category IDs)
- OpenRouter Node — Generates topic and meta info
- OpenAI Node — Generates full article and image
- WordPress Node — Publishes post
- Discord Node — Sends publish alert
- HTTP Request Node — Handles image upload or utility calls
🛠️ Customization Tips
| Feature | How to Customize | | ----------------- | ---------------------------------------------------- | | Categories | Update category IDs in the WordPress Post Draft node | | Schedule | Modify the interval in the Schedule Trigger | | Tone & Style | Adjust prompts in the LLM Chain node | | Notifications | Add Slack, Email, or other channels | | Image Style | Change OpenAI prompt for “vivid”, “natural”, etc. |
📦 Pre-Requirements
- n8n Instance (Cloud/Self-hosted)
- Install:
@n8n/n8n-nodes-langchain - All required API credentials configured
- WordPress categories set
- Admin user ID available
🔧 Nodes Used
Telegram TriggerSchedule TriggerOpenRouterOpenAIWordPressDiscordHTTP Request
✅ Test the Workflow
- Deploy and connect your n8n instance.
- Send
/generateto your Telegram bot. - Check your WordPress site for the newly published post!
Made by: Khaisa Studio
Tag: youtube, summarizer, telegram, openai
Category: AI Automation, Video Tools
Need a custom? contact me on LinkedIn or Web
n8n Workflow: AI-Powered SEO Blog Post Generation and WordPress Publishing
This n8n workflow automates the entire process of generating SEO-optimized blog posts using AI and publishing them directly to your WordPress site. It leverages large language models (LLMs) to create content based on a schedule, with optional human approval steps via Telegram or Discord.
What it does
This workflow streamlines your content creation pipeline through the following steps:
- Scheduled Trigger: The workflow is initiated on a predefined schedule, ensuring a consistent content publishing cadence.
- AI Content Generation: It uses an AI Chat Model (configurable for OpenAI, Google Gemini, or OpenRouter) to generate blog post content.
- Structured Output Parsing: The AI-generated content is then parsed to extract structured data, ensuring it meets the requirements for a blog post (e.g., title, body, tags).
- Human-in-the-Loop (Optional):
- The generated content can be sent to a Telegram chat for review and approval.
- Alternatively, it can be sent to a Discord channel for review and approval.
- An "If" node checks for approval before proceeding to publishing.
- WordPress Publishing: Upon approval (or if the human-in-the-loop step is skipped), the SEO-optimized blog post is automatically published to your WordPress site.
- Error Handling/Notifications: (Implicit, though not explicitly shown in this JSON, a robust workflow would typically include notifications for failures).
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- AI Chat Model Credentials:
- OpenAI API Key (for OpenAI Chat Model)
- Google Gemini API Key (for Google Gemini Chat Model)
- OpenRouter API Key (for OpenRouter Chat Model)
- WordPress Account: Access to a WordPress site with appropriate user permissions for publishing posts. You'll need to configure WordPress credentials in n8n.
- Telegram Bot Token and Chat ID (Optional, for human approval via Telegram)
- Discord Webhook URL or Bot Token (Optional, for human approval via Discord)
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- Locate the "Basic LLM Chain" node and configure your preferred AI Chat Model (OpenAI, Google Gemini, or OpenRouter) with your respective API key.
- Locate the "Wordpress" node and set up your WordPress credentials (API Key or username/password).
- If using human approval:
- For Telegram: Configure the "Telegram Trigger" and "Telegram" nodes with your Telegram Bot Token and Chat ID.
- For Discord: Configure the "Discord" node with your Discord Webhook URL or Bot Token.
- Customize Content Generation:
- Adjust the prompt within the "Basic LLM Chain" node to guide the AI in generating your desired SEO-optimized blog posts.
- Modify the "Structured Output Parser" node if your desired output structure from the AI changes.
- Configure Schedule:
- Set the desired schedule in the "Schedule Trigger" node (e.g., daily, weekly).
- Activate the Workflow: Once all configurations are complete, activate the workflow.
This workflow provides a powerful foundation for automating your content marketing efforts, allowing you to scale blog post production efficiently.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
By Matt@VeraisonLabsSend WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
By RapiwaTrack SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.
By Rahul Joshi