HumationHuman + Automation
Back to Catalog

Auto-Generate & Publish SEO Blog Posts to WordPress with OpenRouter & Runware

Khairul MuhtadinKhairul Muhtadin
1225 views
2/3/2026
PuppeteerS3WebpageAutomationPDF
Official Page

Automate Blog Creation and Publishing with Ultra-Low Cost AI

This n8n workflow — BlogBlizt: Runaware Edition — automates the creation, enrichment, and publishing of SEO-optimized blog posts for WordPress using entirely free OpenRouter AI models for text and metadata generation, plus ultra-low-cost Runware AI for realistic featured images (as low as $0.0016 per image).

It’s triggered every 3 hours or manually via Telegram. Each run generates 1,500–3,500-word articles on trending topics in Technology, AI, Tech Facts, History, or Tips — all complete with catchy titles, slugs, meta descriptions, and visuals.

💰 Why This Is So Cost-Efficient

  • ✅ Free metadata + article generation (OpenRouter free-tier models)
  • 💸 Only cost is for image generation via Runware:
    • Image generation: ~$0.0016/image (the cheapest model could be $0,00065)

This is ideal for scale — generating dozens of high-quality blog posts with minimal expense.

⚡ Who Is This For?

  • Bloggers who want high-quality content without writing
  • SEO marketers seeking fresh, long-form articles
  • WordPress site owners automating publishing workflows
  • Growth hackers targeting high-volume content generation

❓ What Problem Does It Solve?

Creating SEO-rich blog content is time-consuming, expensive, and requires expertise. BlogBlizt eliminates this friction by using free models (OpenRouter) to generate text and metadata — making this workflow nearly free to operate, with the only cost being the featured image (~$0.0016/image).

🔧 What This Workflow Does

  • ⏱ Triggers: Every 3 hours (or via Telegram command: generate)
  • 🧠 Generates Metadata: Title, slug, category, focus keyphrase, and meta description using OpenRouter
  • ✍️ Writes SEO Article: 1,500–3,500 words with headings, H2/H3s, CTA, and outbound links
  • 🖼️ Creates Image: Generates realistic 1024×1024 blog image with Runware AI
  • 📤 Publishes to WordPress: Auto-publishes with category ID, featured image, and Yoast SEO fields
  • 📣 Notifies: Sends publish link to Discord and Telegram (optional)

🔐 Setup Instructions

  • Import .json into n8n
  • Add credentials:
    • OpenRouter API (free LLMs like LLaMA-3, Nemotron)
    • Runware API key (get it here)
    • (Optional) Telegram Bot + Discord Webhook
  • Test by sending the word generate via Telegram

🧩 Pre-Requirements

  • Self-hosted or cloud-based n8n instance
  • WordPress with category IDs configured:
    • Technology → 3
    • AI → 4
    • Tech Fact → 7
    • Tech History → 8
    • Tech Tips → 9
  • OpenRouter API Key (free)
  • Runware API Key (for images)
  • WordPress user ID (admin, default is 1)
  • Telegram bot (optional)
  • Discord webhook (optional)

🛠️ Customize It Further

  • Change writing tone or prompt in ✍️ Compose SEO Article Content node
  • Cofigure the category
  • Swap free LLMs (Claude, Gemini, GPT, etc.) in OpenRouter settings
  • Adjust schedule (every 6h, daily, etc.)
  • Extend alerts (email, Slack, Notion)

🧠 Nodes Used

  • Schedule Trigger
  • Telegram Trigger
  • @n8n/n8n-nodes-langchain (OpenRouter)
  • WordPress Node
  • HTTP Request (Runware API)
  • Discord Webhook
  • Sticky Notes (Documentation inside canvas)

📞 Support

Created by: Khaisa Studio
Tag: youtube, summarizer, telegram, openai
Category: AI Automation, Video Tools Need a custom? contact me on LinkedIn or Web

n8n Workflow: Auto-Generate and Publish SEO Blog Posts to WordPress with OpenRouter/Runware

This n8n workflow automates the creation and publishing of SEO-optimized blog posts to WordPress, leveraging advanced AI models via OpenRouter or Google Gemini. It simplifies content generation, allowing you to regularly populate your WordPress site with fresh, relevant articles.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow starts at predefined intervals (e.g., daily, weekly) to ensure a consistent content publishing schedule.
  2. Generates Blog Content with AI: It utilizes a Basic LLM Chain to interact with a large language model (LLM) for content generation.
    • It can be configured to use either OpenRouter Chat Model (allowing access to various models like OpenRouter, Runware, etc.) or Google Gemini Chat Model for generating blog post titles, outlines, and full article content.
    • A Structured Output Parser ensures the AI-generated content adheres to a predefined JSON structure, making it easy to extract and use.
  3. Publishes to WordPress: The generated and structured blog post content is then automatically published to your WordPress site.
  4. Notifies on Completion (Optional): After publishing, the workflow can send notifications to Telegram or Discord channels, informing you about the new post.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • WordPress Account: Access to a WordPress site with API publishing enabled.
  • AI Model Access:
    • OpenRouter API Key: If using the OpenRouter Chat Model (which allows access to models like OpenRouter, Runware, etc.).
    • Google Gemini API Key: If using the Google Gemini Chat Model.
  • Telegram Bot Token and Chat ID (Optional): For Telegram notifications.
  • Discord Webhook URL (Optional): For Discord notifications.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file for this workflow.
    • 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.
  2. Configure Credentials:
    • WordPress: Create or update your WordPress credentials in n8n, providing your WordPress URL, username, and application password.
    • AI Model:
      • For OpenRouter Chat Model: Create an "OpenRouter API" credential in n8n and enter your API key.
      • For Google Gemini Chat Model: Create a "Google Gemini API" credential in n8n and enter your API key.
    • Telegram (Optional): Create a "Telegram API" credential with your Bot Token.
    • Discord (Optional): Create a "Discord API" credential with your Webhook URL.
  3. Customize AI Prompts and Schema:
    • Open the "Basic LLM Chain" node.
    • Review and adjust the prompts within the "OpenRouter Chat Model" or "Google Gemini Chat Model" nodes to guide the AI in generating content specific to your niche and SEO requirements (e.g., target keywords, desired tone, blog post length).
    • Verify the "Structured Output Parser" schema matches the expected output format from your LLM prompt.
  4. Configure WordPress Publishing:
    • Open the "Wordpress" node.
    • Select the appropriate WordPress credential.
    • Map the AI-generated fields (e.g., title, content, categories) to the corresponding WordPress post fields.
  5. Configure Notifications (Optional):
    • Open the "Telegram" and/or "Discord" nodes.
    • Select your configured credentials.
    • Customize the message content to include details about the newly published post.
  6. Set Schedule:
    • Open the "Schedule Trigger" node.
    • Define how often you want the workflow to run (e.g., every day, once a week).
  7. Activate the Workflow:
    • Once all configurations are complete, save the workflow and activate it.

The workflow will now automatically generate and publish blog posts to your WordPress site according to your defined schedule and AI prompts.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942