🤖 WordPress Blog Automation Workflow

🛠 SETUP (do once before running the flow)

1 · DOMAIN

Add one variable anywhere before the workflow starts (via Set node, .env, or instance config):

DOMAIN=https://your-wordpress-site.com

This will be used in all WordPress REST API calls.

2 · CREDENTIALS (create in n8n → Credentials)

| Credential Name | Purpose | Minimum Scope | |-----------------|---------|---------------| | YOUR_WORDPRESS_CREDENTIAL | WordPress API | POST /media, POST /posts | | YOUR_POSTGRES_CREDENTIAL | PostgreSQL access for used categories | DB + table created in step 3 | | YOUR_OPENAI_CREDENTIAL | OpenAI key for GPT | GPT-4-mini or better |

🧠 Keep the names exactly — the workflow references them directly.

3 · POSTGRESQL (one-time bootstrap)

🖥️ Terminal method (fastest — paste into sudo -u postgres psql)

-- 3-A · Create database and user
CREATE DATABASE n8n_blog;
CREATE USER n8n_writer WITH PASSWORD 'S3cur3-Pa55';
GRANT ALL PRIVILEGES ON DATABASE n8n_blog TO n8n_writer;
\c n8n_blog n8n_writer  -- Reconnect to DB as the new user

-- 3-B · Create the tracking table
CREATE TABLE IF NOT EXISTS public.used_categories (
  category_id INTEGER PRIMARY KEY,
  name        TEXT,
  description TEXT,
  title       TEXT,
  used_at     TIMESTAMPTZ
);
GRANT INSERT, UPDATE, SELECT ON public.used_categories TO n8n_writer;

🔗 Then configure the credential in n8n

Name:       YOUR_POSTGRES_CREDENTIAL
Host:       127.0.0.1
Port:       5432
Database:   n8n_blog
User:       n8n_writer
Password:   S3cur3-Pa55
Schema:     public

💡 No terminal access?
Create a temporary Postgres → Execute Query node with the same SQL, run once, then delete it.

4 · FIRST TEST

Run the first 3–5 nodes manually to verify:

• ✅ WordPress auth works
• ✅ DB connection + writing works
• ✅ GPT responds as expected

Once confirmed, enable the Schedule Trigger to automate.

✅ WHAT THIS WORKFLOW DOES

• Loads all WP categories and filters out excluded ones
• Picks the least-used category from your DB
• Generates a unique, well-structured WP article using GPT (TOC, blocks, CTA)
• Generates a cover image and uploads it to /media
• Publishes the post to /posts and updates usage in your PostgreSQL DB

⏰ Triggers this workflow every few hours.

📥 Loads all WordPress categories.

🧹 Filters out excluded category IDs.

Choose them yourself, some categories are not for AI Agent, like reviews or same

🗃 Loads recently used categories from DB.

🎯 Picks least-used category for next post.

📄 Loads 10 latest article titles for the selected category.

🧠 Generates a unique article title with GPT.

🧾 Prepares the new article title.

🔀 Merges category + title data.

📦 Combines all post metadata into one object.

📝 Saves used category and title to DB.

✍️ Writes full WordPress-style HTML article.

🧾 Extracts content block from AI output.

🖼 Prepares a placeholder cover image URL.

⬇️ Downloads the cover image.

📤 Uploads image to WordPress media.

🔗 Merges image + content + category info.

📬 Prepares final JSON body for the WP post.

🚀 Publishes post to your WordPress site.

Make sure:

• Your WordPress site allows public access to /wp-json/wp/v2/categories
• You have at least 1 category created
• No security plugin (like Wordfence) is blocking REST API

No credential needed for public category fetch.

Make sure:

• You've created the table (see setup note)
• Credential YOUR_POSTGRES_CREDENTIAL is configured
• DB user has SELECT rights on the table

Tip: This selects the least recently used category for the next post.

! Set your WordPress domain inside the “Config” Set node.

Auto WordPress Blog Generator (GPT + Postgres + WP Media)

Purpose and structure

This folder contains the Auto WordPress Blog Generator (GPT + Postgres + WP Media) workflow. Its executable nodes use agent, code, httpRequest, lmChatOpenAi, merge, noOp, postgres, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Schedule Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Postgres/0263_Postgres_Code_Automation_Webhook.json MIT; preserve source notices.