Perplexity + WordPress: researched posts published fast
Researching a topic, outlining a post, formatting it for WordPress, then remembering to tell your team in Slack sounds simple. In practice, it turns into tab chaos, half-finished drafts, and “I’ll publish it later” that never happens.
This Perplexity WordPress automation hits content marketers hardest, but solo founders and small agency teams feel it too. You get a repeatable flow that turns research into a live WordPress post and sends the link out automatically, so your publishing cadence stops depending on your mood and spare time.
Below is what the workflow does, what you’ll need, and what to tweak so it fits your niche (tech, AI, automation, or anything else you publish often).
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Perplexity + WordPress: researched posts published fast
flowchart LR
subgraph sg0["Chat Message Flow"]
direction LR
n0["<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/>Perplexity Insight Pull"]
n1@{ icon: "mdi:play-circle", form: "rounded", label: "Chat Message Trigger", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Slack Tools List", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Content Authoring Agent", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Format Research Summary", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Post to WordPress", pos: "b", h: 48 }
n6@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch Email Alert", pos: "b", h: 48 }
n7@{ icon: "mdi:cog", form: "rounded", label: "Slack Publish Notice", pos: "b", h: 48 }
n8@{ icon: "mdi:brain", form: "rounded", label: "GPT SEO Draft Builder", pos: "b", h: 48 }
n9["<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/form.svg' width='40' height='40' /></div><br/>Research Form Trigger"]
n10@{ icon: "mdi:swap-vertical", form: "rounded", label: "Configure Workflow Inputs", pos: "b", h: 48 }
n11@{ icon: "mdi:cog", form: "rounded", label: "Notion Tools List", pos: "b", h: 48 }
n12@{ icon: "mdi:cog", form: "rounded", label: "Add Notion Entry", pos: "b", h: 48 }
n2 -.-> n3
n11 -.-> n3
n0 --> n4
n7 -.-> n3
n4 --> n10
n10 --> n3
n6 -.-> n3
n12 -.-> n3
n1 --> n3
n5 -.-> n3
n8 -.-> n3
n9 --> n0
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 n1,n9 trigger
class n3 ai
class n8 aiModel
class n0 api
classDef customIcon fill:none,stroke:none
class n0,n9 customIcon
The Problem: Research-to-publish takes too many tools
Publishing consistently is rarely blocked by “not knowing what to write.” It’s the messy middle. You research a topic, grab sources, paste notes into a doc, ask AI to draft something, then you still have to clean up headings, add a meta description, log the post somewhere, and tell the team it’s live. If you do this a few times a week, you start cutting corners. Posts ship without structure, internal tracking gets skipped, and promotion becomes an afterthought. Honestly, that’s how a “content plan” quietly turns into random posting.
Small friction points don’t stay small when you repeat them.
- Research gets trapped in chat threads or browser tabs, so you redo it the next time.
- WordPress formatting takes longer than writing the actual first draft, especially if you want clean H1/H2 structure.
- Team visibility breaks down because Slack notifications are manual, which means posts go live with zero momentum.
- Tracking is inconsistent, so you can’t answer simple questions like “What did we publish last week?” without hunting.
The Solution: Perplexity research → WordPress post → Slack notification
This workflow automates your content pipeline from “topic idea” to “published link in Slack.” It starts with a simple trigger (a form submission or a chat message) where you enter a topic and any angle you want to focus on. Perplexity AI then pulls up-to-date research and key points, which the workflow formats into a clean summary you can reuse. Next, GPT-4 generates a short SEO-ready draft with structure (H1, H2 sections, plus a meta description). Once the draft is prepared, n8n publishes it to WordPress automatically, logs the details to a Notion database, and notifies you in Slack so the team sees it immediately.
The workflow begins when you submit a research prompt. From there, Perplexity collects fresh context, GPT turns it into a properly structured post, and WordPress receives the finished content. Finally, Slack (and optionally Gmail) gets the title and URL so promotion can start right away.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish 3 posts a week. Manually, research is often about 45 minutes, drafting and formatting in WordPress is about 60 minutes, and then logging + Slack sharing is another 10 minutes. Call it roughly 2 hours per post, or about 6 hours weekly. With this workflow you spend maybe 10 minutes writing a good prompt, then wait for processing and approve the result. Most weeks, you’ll get about 4–5 hours back and still ship posts that look consistent.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Perplexity API for up-to-date research and sources
- OpenAI (GPT-4) API to draft SEO-structured content
- WordPress with API access to publish posts
- Slack to notify a channel with the live URL
- Notion database to log title, URL, and metadata
- Gmail API credentials (optional) for email alerts
- Community node: n8n-nodes-mcp (install via Settings → Community Nodes)
Skill level: Intermediate. You won’t write code, but you will connect APIs, map a few fields, and test runs end-to-end.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A form submission or chat message kicks things off. You enter a topic (and optionally an angle, audience, or keyword) using the workflow’s Research Form Trigger or Chat Message Trigger.
Perplexity gathers the research. n8n sends your prompt through an HTTP request to Perplexity, then cleans the response into a formatted research summary so it’s easy for the writing model to use.
GPT turns research into a publishable draft. The workflow passes inputs into the content authoring agent and the GPT SEO draft builder so the output includes headings, a short meta description, and a post body you can actually ship.
Publishing and notifications happen automatically. n8n posts the content to WordPress, creates a matching log entry in Notion, and sends the live URL to Slack (with Gmail alerts available if you want an inbox trail).
You can easily modify the research prompt to match your niche, or switch the Slack channel based on category. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
This workflow can be initiated by chat input or a research form submission. Start by configuring the chat trigger used to kick off the authoring agent.
- Add and open Chat Message Trigger.
- Keep default options unless you need custom chat settings.
- Connect Chat Message Trigger to Content Authoring Agent as shown in the workflow.
Step 2: Configure the Form Trigger for Research Intake
The research pipeline starts with a form submission that provides the topic or question.
- Add and open Research Form Trigger.
- Set Form Title to
AutoBlog Creator. - Set Form Description to
From research to article — no writing required. - Ensure the field label is Topic or Question with placeholder
=How is GPT-4 transforming content creation in 2025?. - Connect Research Form Trigger to Perplexity Insight Pull.
Step 3: Connect Perplexity Research and Formatting
These nodes fetch research from Perplexity and format the summary for the agent prompt.
- Open Perplexity Insight Pull and set URL to
https://api.perplexity.ai/chat/completions. - Set Method to
POSTand enable Send Body with Specify Body set tojson. - Set JSON Body to the provided expression:
={ "model": "sonar-pro", "messages": [ { "role": "system", "content": "Act as a professional news researcher who is capable of finding detailed summaries about a news topic from highly reputable sources." }, { "role": "user", "content": " Research the following topic and return everything you can find about: '{{ $json['Topic or Question'] }}'." } ] }. - Credential Required: Connect your httpHeaderAuth credentials in Perplexity Insight Pull.
- Open Format Research Summary and confirm the research field uses the expression
{{ $json.choices[0].message.content.replaceAll("[1]", " - source: " +$json.citations[0]).replaceAll("[2]"," - source:" +$json.citations[1]).replaceAll("[3]"," - source: " +$json.citations[2]).replaceAll("[4]"," - source: "+$json.citations[3]).replaceAll("[5]"," - source: "+$json.citations[4]).replaceAll("[6]"," - source: "+$json.citations[5]).replaceAll("[7]"," - source: "+$json.citations[6]).replaceAll("[8]"," - source: "+$json.citations[7]).replaceAll("[9]"," - source: "+$json.citations[8]).replaceAll("[10]"," - source: "+$json.citations[9]) }}. - Connect Perplexity Insight Pull → Format Research Summary → Configure Workflow Inputs.
Tip: If your Perplexity response structure differs, the choices[0].message.content or citations paths may need adjustment.
Step 4: Set Up the AI Authoring Agent
The agent orchestrates content creation, publishing, email alerts, and Slack/Notion updates.
- Open Configure Workflow Inputs and set values for emailAddress, slackChannelId, and notionDatabaseId (leave blank only if you plan to map them dynamically).
- Open Content Authoring Agent and confirm the prompt includes the research summary expression
{{ $('Format Research Summary').item.json.research }}. - Confirm the agent uses the inputs
{{ $json.emailAddress }},{{ $json.slackChannelId }}, and{{ $json.notionDatabaseId }}. - Ensure GPT SEO Draft Builder is connected as the language model for Content Authoring Agent.
- Credential Required: Connect your openAiApi credentials in GPT SEO Draft Builder. This is the AI model used by Content Authoring Agent.
⚠️ Common Pitfall: AI tool nodes like Slack Tools List and Add Notion Entry should not be used directly; their credentials must be configured on the tool node while the execution is controlled by Content Authoring Agent.
Step 5: Configure Publishing and Notification Tools
The agent calls these tools to publish content, send email alerts, and log details to Slack and Notion.
- Open Post to WordPress and set Title to
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Title', ``, 'string') }}and Content to{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Content', ``, 'string') }}with Statuspublish. - Credential Required: Connect your wordpressApi credentials in Post to WordPress.
- Open Dispatch Email Alert and confirm fields use AI expressions for Send To, Subject, and Message:
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('To', ``, 'string') }},{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Subject', ``, 'string') }},{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Message', ``, 'string') }}. - Credential Required: Connect your gmailOAuth2 credentials in Dispatch Email Alert.
- Open Slack Tools List and Slack Publish Notice; both should use mcpClientApi credentials.
- Credential Required: Connect your mcpClientApi credentials in Slack Tools List and Slack Publish Notice.
- Open Notion Tools List and Add Notion Entry and connect mcpClientApi credentials.
- Verify Slack Publish Notice uses Tool Name
{{ $fromAI("tool", "the tool selected") }}and Tool Parameters{{ $fromAI('Tool_Parameters', ``, 'json') }}. - Verify Add Notion Entry uses Tool Name
{{ $fromAI("tool", "the tool selected") }}and Tool Parameters{{ $fromAI('tool_parameters', ``, 'json') }}.
These tools are called by Content Authoring Agent, so ensure they remain connected as AI tools rather than standard execution links.
Step 6: Test and Activate Your Workflow
Run an end-to-end test to verify research collection, content creation, publishing, and notifications.
- Click Execute Workflow and submit a test entry through Research Form Trigger with a realistic topic.
- Confirm Perplexity Insight Pull returns a response and Format Research Summary outputs a clean research field.
- Verify Content Authoring Agent creates content and calls Post to WordPress, Dispatch Email Alert, Slack Publish Notice, and Add Notion Entry.
- Successful execution looks like: a published WordPress post, a sent email, a Slack notification in the target channel, and a new Notion database entry.
- Once confirmed, toggle the workflow to Active to run in production.
Common Gotchas
- WordPress credentials can expire or lack the right permissions. If publishing fails, check your WordPress application password (or API user role) first.
- If you’re using Wait behavior indirectly (slow research calls or model responses), processing times vary. Bump up any timeouts or retry logic 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
About 30 minutes once you have your API keys.
No coding required. You’ll mostly connect accounts, paste API keys, and map a few fields like title and body.
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 and Perplexity API usage based on how often you generate posts.
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.
Yes. Update the prompt inside the GPT SEO Draft Builder and Content Authoring Agent so it matches your tone, formatting rules, and desired length. Common tweaks include adding a “style guide” paragraph, forcing specific H2 sections (like “Key Takeaways”), and generating categories/tags for WordPress. You can also adjust the form inputs so each request includes a keyword, audience, and CTA.
Usually it’s authentication. Regenerate your WordPress application password (or confirm the API user still has author/editor permissions) and update the credential in n8n. If the post is created but empty, check your field mapping for title/content and confirm the AI output is plain text, not a nested object. Rate limiting is rarer here, but it can show up if you publish a lot in a short burst.
On n8n Cloud, it depends on your monthly execution limit and how many runs you trigger. If you self-host, there’s no built-in cap; it mostly comes down to your server size and your Perplexity/OpenAI usage budgets.
Often, yes, because you can keep the whole flow in one place and add branching logic without paying extra for every little step. Self-hosting is the big difference if you publish frequently. Another factor is the community node used here (n8n-nodes-mcp), which is specific to n8n and won’t translate directly to Zapier. Zapier or Make can still work if you only need a very simple Perplexity → WordPress handoff and don’t care about Notion logging. If you want help picking the right setup for your volume and team workflow, Talk to an automation expert.
Once this is running, publishing stops being a multi-tool chore. The workflow handles the repeatable parts, and you get your time (and momentum) back.
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.
