January 22, 2026

OpenAI to WordPress, blog posts published consistently

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Publishing “consistently” sounds great until you’re staring at an empty draft at 9pm, copying chunks from notes, fixing headings, and redoing formatting you already did last week. Then you miss a week. Then two. And the blog quietly turns into a guilt project.

This is the kind of mess that slows down marketing managers trying to hit content goals, but founders and agency teams feel it too. With OpenAI WordPress automation, you can turn a short prompt or a schedule into publish-ready posts without living inside the editor.

Below you’ll see how the workflow runs, what it replaces in your process, and what you can tweak so the posts still sound like you (not a generic template).

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: OpenAI to WordPress, blog posts published consistently

Click to explore

flowchart LR

    subgraph sg0["Scheduled Automation Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "Chat Input Trigger", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Select Input Text"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Chat Extract Slugs"]
        n4@{ icon: "mdi:cog", form: "rounded", label: "Chat Convert Sitemap", pos: "b", h: 48 }
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Chat Fetch Sitemap"]
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Schedule Fetch Sitemap"]
        n7@{ icon: "mdi:cog", form: "rounded", label: "Schedule Parse Sitemap", pos: "b", h: 48 }
        n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Schedule Extract Slugs"]
        n9@{ icon: "mdi:robot", form: "rounded", label: "Schedule Topic Suggestion", pos: "b", h: 48 }
        n10@{ icon: "mdi:robot", form: "rounded", label: "Generate Draft Post", pos: "b", h: 48 }
        n11@{ icon: "mdi:robot", form: "rounded", label: "Edit and Validate Post", pos: "b", h: 48 }
        n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/wordpress.svg' width='40' height='40' /></div><br/>Publish to WordPress"]
        n10 --> n11
        n11 --> n12
        n1 --> n5
        n2 --> n10
        n0 --> n6
        n5 --> n4
        n3 --> n2
        n4 --> n3
        n6 --> n7
        n8 --> n9
        n7 --> n8
        n9 --> n2
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0,n1 trigger
    class n9,n10,n11 ai
    class n5,n6 api
    class n2,n3,n8 code
    classDef customIcon fill:none,stroke:none
    class n2,n3,n5,n6,n8,n12 customIcon

The Problem: Consistent blogging turns into a weekly scramble

A blog isn’t hard because writing is hard. It’s hard because the work shows up in little chunks all week. You need a topic, a draft, a quick SEO pass, a clean WordPress layout, then the final publish. When you do it manually, it steals the “in-between” time that you thought you had. And the worst part is the context switching: you go from creative thinking to admin work to formatting to “wait, where’s that old link?” Realistically, one post can eat about 2–4 hours even when you’re moving fast.

The friction compounds. Here’s where it breaks down.

You keep postponing publishing because the last 20% (formatting, links, headings) feels endless.
Ideas die in notes because turning them into a structured draft takes a full focused block of time.
Quality gets inconsistent when you rush, which means more editing and second-guessing later.
WordPress publishing becomes a separate chore, so drafts pile up and nothing goes live.

The Solution: AI drafts + editorial polish + auto-publish to WordPress

This n8n workflow connects OpenAI and WordPress so posts go from “input” to “published” with far less manual effort. You can run it on a schedule (hands-off) or trigger it from a chat-style prompt (fast and flexible). In scheduled mode, the workflow checks your site map, generates a topic idea that fits your site, then writes a full draft. In prompt mode, you feed it a short phrase (even one or two words) and it builds the article from that seed. After the draft, an editorial pass cleans up structure, tone, and basic SEO elements before the post is published straight to your WordPress site through the API.

The workflow starts with either a scheduled trigger or a chat intake message. It then gathers context from your WordPress site (via sitemap requests and parsing), generates the content in a few AI stages, and pushes the finished article into WordPress as a new post. No copy-paste. No reformatting marathons.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It accepts either a scheduled run or a short prompt as the starting point.
It pulls your site structure via sitemap requests, then extracts usable context.
It generates a topic, writes a full draft, and runs an editorial revision pass.
It publishes the final content to WordPress through the WordPress API.

Most teams get a publishable first draft in about 5 minutes once configured.
Your blog stays active even when the week gets chaotic.
You reduce last-minute formatting errors because the output is already structured.
Editors can spend time improving ideas instead of cleaning up basics.
You can scale from “occasional posts” to a real cadence without hiring immediately.

Example: What This Looks Like

Say you publish 3 posts a week. Manually, a “quick” post is still about 3 hours when you include outlining, drafting, cleanup, and WordPress formatting, so that’s roughly 9 hours weekly. With this workflow, you can spend about 10 minutes dropping prompts or reviewing topic ideas, then let the AI writing + editorial pass run and publish in the background (usually within about 5 minutes per post). You still review when it matters, but you’re no longer donating a full day every week to production.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
OpenAI for topic generation, drafting, and editing
WordPress to publish posts via API access
OpenAI API key (get it from your OpenAI account dashboard)

Skill level: Intermediate. You’ll connect accounts, add API credentials, and tweak prompts so the output matches your brand.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Scheduled run or chat prompt kicks things off. You can let it run on a timetable with the Scheduled Run Trigger, or you can start it by sending a short topic prompt through the Chat Intake Trigger.

Your site context gets pulled automatically. The workflow requests your sitemap (HTTP Request), parses it (XML), and extracts slugs, so the AI can reference what you already publish and avoid repeating itself.

OpenAI generates the content in stages. One node creates a topic idea (useful for scheduled mode), another builds the full draft, and a final “editorial review” pass tightens tone and structure before anything goes live. Honestly, this staged approach is what makes it feel less like raw AI output.

WordPress receives a ready-to-publish post. The final node publishes directly to your WordPress site through the API, so the draft becomes an actual post without you touching the editor.

You can easily modify the prompts to match your voice or adjust publishing frequency based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Trigger Type

Set up both entry points so the workflow can run on a schedule or from a chat-triggered request.

Open Scheduled Run Trigger and define the schedule under Rule to match your desired cadence.
Open Chat Intake Trigger and keep Allow File Uploads set to false unless you want file inputs.
Confirm the execution flow for triggers: Scheduled Run Trigger → Scheduled Sitemap Request and Chat Intake Trigger → Chat Sitemap Request.

Use the scheduled trigger for automated publishing and the chat trigger for on-demand drafts or topic prompts.

Step 2: Connect the Sitemap Data Source

Both entry paths fetch and parse your sitemap so the workflow can extract existing slugs and avoid duplicate topics.

In Scheduled Sitemap Request, set URL to https://bruzzi.online/sitemap.xml.
In Chat Sitemap Request, set URL to https://bruzzi.online/sitemap.xml.
Keep Scheduled Sitemap Parser and Chat Sitemap Parser as-is to parse XML into JSON.
Verify parsing flows: Scheduled Sitemap Request → Scheduled Sitemap Parser → Scheduled Slug Extractor and Chat Sitemap Request → Chat Sitemap Parser → Chat Slug Extractor.

⚠️ Common Pitfall: If your sitemap URL changes, update it in both Scheduled Sitemap Request and Chat Sitemap Request or the parser will receive empty data.

Step 3: Set Up Input Selection and Slug Extraction

This layer unifies inputs from either chat or scheduled topic generation and extracts slug lists used by the AI prompts.

In Scheduled Slug Extractor, keep the JavaScript logic that maps items[0].json.urlset.url into slugs.
In Chat Slug Extractor, keep the same JavaScript logic to extract slugs from the chat-requested sitemap.
In Select Input Source, keep the JavaScript that outputs result from either $json.chatInput or $json.message.content.
Confirm routing: Chat Slug Extractor → Select Input Source and Generate Topic Idea → Select Input Source.

The Select Input Source node allows you to feed either a chat-provided topic or an AI-generated topic into the same drafting pipeline.

Step 4: Set Up AI Content Generation

Configure the three AI steps to generate the topic, draft the article, and run editorial refinement.

Open Generate Topic Idea and keep the model selection gpt-5-nano. Credential Required: Connect your openAiApi credentials.
In Generate Topic Idea, keep the prompt content that references {{ $json.slugs }} so existing topics are avoided.
Open Draft Article Builder and keep the model selection gpt-4o-mini-search-preview. Credential Required: Connect your openAiApi credentials.
Verify the prompt references the selected topic via {{ $('Select Input Source').item.json.result }} and slug list via {{ $json.slugs }}.
Open Editorial Review Pass and keep JSON Output enabled. Credential Required: Connect your openAiApi credentials.
Ensure the prompt in Editorial Review Pass references internal slugs using {{ $('Chat Slug Extractor').item.json.slugs }} and content input via {{ $json.message.content }}.

⚠️ Common Pitfall: If the AI output does not follow the expected JSON structure, the Publish to WordPress mappings will fail. Keep the JSON format requirements intact in the prompts.

Step 4: Configure Output/Action Nodes

Finalize publishing to WordPress using the structured output from the editorial pass.

Open Publish to WordPress and connect the site. Credential Required: Connect your wordpressApi credentials.
Set Title to ={{ $json.message.content.title }}.
Under Additional Fields, set Slug to ={{ $json.message.content.slug }}, Status to publish, and Content to ={{ $json.message.content.content }}.
Confirm the publishing chain: Draft Article Builder → Editorial Review Pass → Publish to WordPress.

If you want drafts instead of immediate publishing, change Status to draft in Publish to WordPress.

Step 5: Test and Activate Your Workflow

Run a controlled test to validate sitemap parsing, AI generation, and WordPress publishing.

Manually execute Scheduled Run Trigger to test the scheduled path or send a test message through Chat Intake Trigger for the chat path.
Confirm Scheduled Sitemap Parser or Chat Sitemap Parser outputs a populated urlset.url structure and that Scheduled Slug Extractor / Chat Slug Extractor produces a slugs array.
Verify Editorial Review Pass returns JSON with title, slug, and content fields.
Check WordPress to confirm a new post appears with the expected title, slug, and HTML content.
When everything looks correct, toggle the workflow to Active to enable production scheduling.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

WordPress credentials can expire or need specific permissions. If things break, check your WordPress Application Passwords (or the user role permissions) first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Frequently Asked Questions

How long does it take to set up this OpenAI WordPress automation automation?

About 5 minutes if your WordPress API access and OpenAI key are ready.

Do I need coding skills to automate OpenAI WordPress automation?

No. You’ll mostly paste credentials and tweak the prompts. The only “technical” part is confirming your WordPress API connection works.

Is n8n free to use for this OpenAI WordPress automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs based on your model and usage.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this OpenAI WordPress automation workflow for draft-only posting instead of auto-publishing?

Yes, but you’ll change one key behavior. In the “Publish to WordPress” node, switch the status from publish to draft so content lands in WordPress for review. You can also tune the “Draft Article Builder” and “Editorial Review Pass” prompts to enforce your structure (intro length, headings, internal links, and CTA style). If you want, keep scheduled mode for drafting, and use prompt mode only when you need a fast one-off post.

Why is my WordPress connection failing in this workflow?

Usually it’s an Application Password issue or the user role can’t create posts. Regenerate the WordPress Application Password, update it in n8n, then confirm the account has permission to publish (or at least create drafts). Also check your WordPress URL in the credentials; http vs https mismatches are a common, annoying cause.

How many posts can this OpenAI WordPress automation automation handle?

On self-hosted n8n, it can handle as many runs as your server can process.

Is this OpenAI WordPress automation automation better than using Zapier or Make?

Often, yes. This workflow relies on multi-step logic (scheduled mode vs prompt mode), pulling and parsing your sitemap, and running a few AI stages before publishing, which is easier to manage in n8n than forcing it into a linear 2–3 step zap. n8n also gives you a real self-hosting option, which matters if you plan to publish frequently and don’t want to pay per task. Zapier or Make can still be fine for very simple “prompt → draft” flows. If you want help choosing, Talk to an automation expert.

Once this is running, your blog stops depending on “finding time to write.” You feed it ideas, review what matters, and WordPress stays active without the copy-paste grind.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "cbc963148f8cd16f730cfba991741deb5e816fa8120bd24be63f85c7fe85930d",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Blog Content Publishing Flow",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-10180",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1100,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "52911348-2e1a-4cb6-af35-c245e2402f25",
"name": "Scheduled Run Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
1000,
130
],
"parameters": {
"rule": {
"interval": [
[]
]
}
},
"typeVersion": 1.2
},
{
"id": "6063c151-0c5c-4f6a-89cc-821be284f634",
"name": "Chat Intake Trigger",
"type": "@n8n/n8n-nodes-langchain.chatTrigger",
"position": [
990,
360
],
"webhookId": "f23328b1-5498-43a4-aed3-2bd0337d29e3",
"parameters": {
"options": {
"allowFileUploads": false
}
},
"typeVersion": 1.1
},
{
"id": "65399934-119e-4f3d-ac0a-9354d2feaa1c",
"name": "Select Input Source",
"type": "n8n-nodes-base.code",
"position": [
140,
350
],
"parameters": {
"jsCode": "// Verifica se `chatInput` existe no JSON\nif ($json.chatInput) {\n  return [{ json: { result: $json.chatInput } }];\n} \n// Caso contr\u00e1rio, verifica se `message.content` existe no JSON\nelse if ($json.message && $json.message.content) {\n  return [{ json: { result: $json.message.content } }];\n}\n// Caso nenhum dos dois existam, retorna um valor padr\u00e3o (opcional)\nelse {\n  return [{ json: { result: 'Nenhuma entrada encontrada' } }];\n}\n"
},
"typeVersion": 2
},
{
"id": "993dc632-d742-4357-9446-cc075d8ff396",
"name": "Chat Slug Extractor",
"type": "n8n-nodes-base.code",
"position": [
320,
410
],
"parameters": {
"jsCode": "// Acessa o array de URLs do JSON\nconst urls = items[0].json.urlset.url;\n\n// Extrai os slugs das URLs\nconst slugs = urls.map(url => {\n  const urlString = url.loc; // Pega o valor da tag <loc>\n  const slug = urlString.split('/').filter(Boolean).pop(); // Extrai a \u00faltima parte da URL\n  return slug;\n});\n\n// Retorna os slugs de forma correta, dentro do formato esperado pelo n8n\nreturn [\n  {\n    json: {\n      slugs: slugs // Aqui a chave 'slugs' \u00e9 um array de slugs extra\u00eddos\n    }\n  }\n];\n"
},
"typeVersion": 2
},
{
"id": "46e54e20-4292-4e00-8531-c7930d616111",
"name": "Chat Sitemap Parser",
"type": "n8n-nodes-base.xml",
"position": [
500,
350
],
"parameters": {
"options": []
},
"typeVersion": 1
},
{
"id": "508fe15b-f0f7-4cbf-9d17-0b67794c43cf",
"name": "Chat Sitemap Request",
"type": "n8n-nodes-base.httpRequest",
"position": [
740,
400
],
"parameters": {
"url": "https://bruzzi.online/sitemap.xml",
"options": []
},
"typeVersion": 4.2
},
{
"id": "861bbd03-9f34-4c00-9df5-344a009e4634",
"name": "Scheduled Sitemap Request",
"type": "n8n-nodes-base.httpRequest",
"position": [
750,
170
],
"parameters": {
"url": "https://bruzzi.online/sitemap.xml",
"options": []
},
"typeVersion": 4.2
},
{
"id": "775fe67d-1146-45a8-ad06-15ce3c0dfed8",
"name": "Scheduled Sitemap Parser",
"type": "n8n-nodes-base.xml",
"position": [
540,
120
],
"parameters": {
"options": []
},
"typeVersion": 1
},
{
"id": "ac79601b-bb46-4b5b-b6b0-781cdd929b13",
"name": "Scheduled Slug Extractor",
"type": "n8n-nodes-base.code",
"position": [
280,
170
],
"parameters": {
"jsCode": "// Acessa o array de URLs do JSON\nconst urls = items[0].json.urlset.url;\n\n// Extrai os slugs das URLs\nconst slugs = urls.map(url => {\n  const urlString = url.loc; // Pega o valor da tag <loc>\n  const slug = urlString.split('/').filter(Boolean).pop(); // Extrai a \u00faltima parte da URL\n  return slug;\n});\n\n// Retorna os slugs de forma correta, dentro do formato esperado pelo n8n\nreturn [\n  {\n    json: {\n      slugs: slugs // Aqui a chave 'slugs' \u00e9 um array de slugs extra\u00eddos\n    }\n  }\n];\n"
},
"typeVersion": 2
},
{
"id": "0cdf1e26-abf1-43dc-973d-21c4c77e3262",
"name": "Generate Topic Idea",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
0,
150
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-5-nano",
"cachedResultName": "GPT-5-NANO"
},
"options": [],
"messages": {
"values": [
{
"content": "=Give me a relevant topic for my blog. I want only the topic. I have a [area] blog for [your persona], and I want something relevant for this audience. Return only the topic.\n\nDo not repeat topics. Below is the list of current topics on my blog. Always focus on a new area/subarea when a topic already exists.\n\nList of existing topics (in slug): {{ $json.slugs }}\n\nReturn only one sentence, without - or other symbols. This will be our topic. Do not send it in slug form.\n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "27b5d043-7dff-4b5a-984c-cc1ddb66c536",
"name": "Draft Article Builder",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
360,
590
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-mini-search-preview",
"cachedResultName": "GPT-4O-MINI-SEARCH-PREVIEW"
},
"options": [],
"messages": {
"values": [
{
"content": "=You are a generator of deep and comprehensive content for a [area] blog. The blog is focused on [your persona]\n\nFrom the provided topic ({{ $('Select Input Source').item.json.result }}), you will write a title, and from that title, you will write a complete blog post. The title must have up to 12 words and up to 60 characters, including spaces.\n\nEnsure the content is highly accurate. It will be read and reviewed by other professionals.\n\nThe current blog topics (slugs) are: {{ $json.slugs }} \u2014 use them throughout the text, along with external links, to increase the reliability of my site. Do not use \u201copenai referrer\u201d or relative links; always use the original link and nothing else. Understand whether I\u2019m sending you a complete piece of content or a specific topic. Feel free to create, recreate, or adjust it according to a relevant, current, and sensible blog theme. The content to be developed in the post is\n\nEnsure you provide the most up-to-date information from guidelines, protocols, directives, articles, and similar relevant online publications when relevant for building this content.\n\nKeywords must be specific objects, places, or atmospheres\u2014not abstract concepts.\n\n**Article Formatting Requirements**\n\n1\ufe0f\u20e3 **Title (H1):** Ensure unique and assertive titles aligned with user search intent.\n2\ufe0f\u20e3 **Subtitles (H2 / H3):** Structure the content for SEO optimization.\n3\ufe0f\u20e3 **Article Structure (Enhanced Readability):**\n\n**Introduction**\nGo straight to the point, avoiding long or generic introductions.\nUse engaging questions or market trend data to capture the reader\u2019s attention.\n\n**Main Content**\nInclude at least three key knowledge points for depth.\nBalance short and long sentences for fluent reading.\nBe thorough, accurate, and descriptive. Ensure the content is extremely relevant and complete, aiming for 3,000\u20137,000 words.\n\nInclude internal links to similar posts distributed throughout the text. \n\nThe base URL for my blog posts is [https://yourblog.com/blog/[slug](https://yourblog.com/blog/[slug)]. Insert 1\u20135 internal links, always matching keywords meaningfully.\n\n**Final Section**\nAvoid generic AI-style summaries; instead, provide insights or practical actions. Do not use the word \u201cconclusion\u201d or similar terms\u2014just complete your reasoning naturally.\n\n**HTML Formatting**\nEnsure the article is properly structured in HTML format:\n\n* Titles: Use <h1>, <h2>, <h3> appropriately.\n* Paragraphs: Wrap text in <p>.\n* Highlighted Words: Use <strong> to emphasize important terms.\n* Lists: Use <ul> and <li> for bullet points.\n  Keep the output clean and well-structured, avoiding plain text. Never include suggestions or comments in your responses.\n\n**Final JSON Format**\n\n```json\n{\n  \"title\": \"{Generate an H1 title aligned with market trends, with high click potential, following the keyword strategy. The title should use capitalization only for the first word or proper nouns'}\",\n  \"content\": \"{Generate a complete article in HTML including H1, H2, H3 titles, paragraphs, lists, etc.}\",\n  \"slug\": \"{Generate a unique, SEO-friendly slug with as few words as possible (minimum of 2), separated by hyphens, such as gina-2025 or 10-better-choices. Do not use accents or similar characters, as they cause issues in some browsers.}\"\n}\n```\n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.6
},
{
"id": "c89b3836-c12d-49fc-8855-d32d4e220069",
"name": "Editorial Review Pass",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
620,
560
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-5-mini",
"cachedResultName": "GPT-5-MINI"
},
"options": [],
"messages": {
"values": [
{
"content": "=You are a WRITER AND EDITOR of content for a [area] blog. The blog is focused on [your persona]\n\nYou will not receive the title, content, or slug \u2014 you will create them to be read by either professionals or laypeople.\n\nYour task is to receive the inputs and return a title, content, and slug, in the provided format.\n\nThe content must be well-written, following correct spelling, grammar, and syntax rules.\n\nIt should be relevant, written by a professional in accessible yet professional language. Ensure the SEO is extremely strong and relevant to the keywords covered in the topic.\n\nThe content must include at least three related keywords throughout the post. Never mention the term \u201ckeywords\u201d or related expressions. They must be inserted contextually and naturally within the text.\n\nThe title should use capitalization only for the first word or proper nouns.\n\nThe post must go straight to the point \u2014 do not use terms like \u201cMain Content,\u201d \u201cContent,\u201d or similar. Always use H2 and H3 for referencing the keyword(s) of the post. The same applies to the conclusion: avoid terms like \u201cConclusion,\u201d \u201cClosing,\u201d or related words. Go directly to your final reasoning. Insert relevant keywords only within the text, in a valid and meaningful context. Never insert them at the end of the text. The post body must contain only the title, slug, and content.\n\nReview and edit all internal links in the post. Consider removing them if they are poorly placed, out of context, or inserted mechanically (for example, \u201cUseful links already inserted in the original text\u201d or \u201cRelevant links I\u2019ve selected for you\u201d). These should be corrected.\n\nEnsure the post contains at least three internal links from my site (formatted as https://yoursite.com/blog/[slug]) in relevant keyword contexts. The available internal link slugs are:\n{{ $('Chat Slug Extractor').item.json.slugs }}\n\nCheck all internal links carefully. Maintain a balance between internal and external links received in your input (minimum of 3 internal and 3 external) to guarantee educational continuity and article reliability, based on both internal and external sources. Never cite any of them in isolation or without context \u2014 they must appear only within meaningful sentences, never as standalone paragraphs for the final reader (whether a medical professional or layperson).\n\nBelow is the complete content of the post to be written, already including external link references:\n{{ $json.message.content }}\n\nReturn the post in HTML format, including title, body, and slug to be used on my blog."
}
]
},
"jsonOutput": true
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.6
},
{
"id": "ee68bb1b-22a1-4a78-8afd-e72961f078d3",
"name": "Publish to WordPress",
"type": "n8n-nodes-base.wordpress",
"position": [
840,
600
],
"parameters": {
"title": "={{ $json.message.content.title }}",
"additionalFields": {
"slug": "={{ $json.message.content.slug }}",
"status": "publish",
"content": "={{ $json.message.content.content }}"
}
},
"credentials": {
"wordpressApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1,
"alwaysOutputData": false
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Draft Article Builder": {
"main": [
[
{
"node": "Editorial Review Pass",
"type": "main",
"index": 0
}
]
]
},
"Editorial Review Pass": {
"main": [
[
{
"node": "Publish to WordPress",
"type": "main",
"index": 0
}
]
]
},
"Chat Intake Trigger": {
"main": [
[
{
"node": "Chat Sitemap Request",
"type": "main",
"index": 0
}
]
]
},
"Select Input Source": {
"main": [
[
{
"node": "Draft Article Builder",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Run Trigger": {
"main": [
[
{
"node": "Scheduled Sitemap Request",
"type": "main",
"index": 0
}
]
]
},
"Publish to WordPress": {
"main": [
[]
]
},
"Chat Sitemap Request": {
"main": [
[
{
"node": "Chat Sitemap Parser",
"type": "main",
"index": 0
}
]
]
},
"Chat Slug Extractor": {
"main": [
[
{
"node": "Select Input Source",
"type": "main",
"index": 0
}
]
]
},
"Chat Sitemap Parser": {
"main": [
[
{
"node": "Chat Slug Extractor",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Sitemap Request": {
"main": [
[
{
"node": "Scheduled Sitemap Parser",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Slug Extractor": {
"main": [
[
{
"node": "Generate Topic Idea",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Sitemap Parser": {
"main": [
[
{
"node": "Scheduled Slug Extractor",
"type": "main",
"index": 0
}
]
]
},
"Generate Topic Idea": {
"main": [
[
{
"node": "Select Input Source",
"type": "main",
"index": 0
}
]
]
}
}
}