January 22, 2026

Google Trends to WordPress, publish posts consistently

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Keeping a blog consistent is brutally manual. You find a topic, check Trends, open ten tabs for research, write, format, upload, add links, grab an image, then still forget to track what went live.

Content managers get stuck chasing deadlines. Marketing leads feel it when “we should publish more” turns into late nights. And if you run a small business, Google Trends automation like this is how you publish without living inside WordPress.

This workflow turns a trending search into a finished WordPress post, complete with research, internal links, and a tracking row in Google Sheets. You’ll see how it works, what you need, and the common places it can wobble.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Trends to WordPress, publish posts consistently

Click to explore

flowchart LR

    subgraph sg0["Schedule 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/>Get Google Trends"]
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Convert Research Format", pos: "b", h: 48 }
        n2@{ icon: "mdi:cog", form: "rounded", label: "Prepare Internal Link Dataset", pos: "b", h: 48 }
        n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Store Cover Image URL", pos: "b", h: 48 }
        n4@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Extract Top 2 Trends", pos: "b", h: 48 }
        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/code.svg' width='40' height='40' /></div><br/>Filter High Volume Keywords"]
        n7@{ icon: "mdi:robot", form: "rounded", label: "Select Best SEO Topic", 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/httprequest.dark.svg' width='40' height='40' /></div><br/>Research Reliable Sources"]
        n9@{ icon: "mdi:robot", form: "rounded", label: "Draft Blog Content", pos: "b", h: 48 }
        n10@{ icon: "mdi:database", form: "rounded", label: "Find Previous Posts", pos: "b", h: 48 }
        n11@{ icon: "mdi:robot", form: "rounded", label: "Insert Internal SEO Links", pos: "b", h: 48 }
        n12@{ icon: "mdi:robot", form: "rounded", label: "Generate Semantic HTML", pos: "b", h: 48 }
        n13@{ icon: "mdi:robot", form: "rounded", label: "Create SEO Slug", pos: "b", h: 48 }
        n14@{ icon: "mdi:robot", form: "rounded", label: "Generate Blog Title", pos: "b", h: 48 }
        n15@{ icon: "mdi:robot", form: "rounded", label: "Create Meta Description", pos: "b", h: 48 }
        n16["<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/>Fetch Cover Image"]
        n17["<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"]
        n18@{ icon: "mdi:database", form: "rounded", label: "Log Published Post", pos: "b", h: 48 }
        n13 --> n14
        n4 --> n0
        n16 --> n3
        n0 --> n5
        n9 --> n10
        n10 --> n2
        n14 --> n15
        n5 --> n6
        n17 --> n18
        n7 --> n8
        n3 --> n17
        n12 --> n13
        n1 --> n9
        n15 --> n16
        n11 --> n12
        n8 --> n1
        n6 --> n7
        n2 --> n11
    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 n4 trigger
    class n7,n9,n11,n12,n13,n14,n15 ai
    class n10,n18 database
    class n0,n8,n16 api
    class n6 code
    classDef customIcon fill:none,stroke:none
    class n0,n6,n8,n16,n17 customIcon

The Problem: Consistent SEO publishing takes too much effort

Publishing “consistently” sounds simple until you do the math. Every post needs a topic with demand, real sources, a clean structure, a meta description, internal links that actually make sense, and an image that won’t look like a placeholder. Most teams end up in a loop: scramble for ideas, write something decent, then lose another hour formatting and uploading it. A week later, nobody remembers which keyword the post targeted or what URL it published to, so optimization turns into guesswork.

The friction compounds. Not because any one step is impossible, but because you repeat the whole sequence again and again.

Trend research gets skipped when you’re busy, so you publish topics people aren’t searching for.
Internal links happen “later,” which usually means never, and the posts don’t support each other.
Formatting inside WordPress eats about an hour per post if you care about clean HTML and headings.
Tracking is scattered, so you can’t easily answer, “What did we publish last month and for which keyword?”

The Solution: Google Trends → researched post → WordPress publish

This n8n workflow runs on a schedule and goes hunting for emerging topics using Google Trends data (via SerpAPI). Once it finds a strong trend, it filters for higher-volume terms, then uses an AI “topic chooser” to pick the best SEO angle based on intent and competitiveness. Next, it pulls credible sources through the Perplexity API so the content has real grounding instead of vibes. From there, AI agents draft the post, insert internal links using your existing post database in Google Sheets, build semantic HTML, generate the slug, write the title and meta description, fetch a cover image, and finally publish directly to WordPress through the REST API. Last step: it logs the published URL, keyword, slug, and other details back into Google Sheets, so you have a clean record you can actually use.

The workflow starts with a scheduled run. Then it moves through trend discovery and research, followed by writing and on-site SEO (internal links, slug, metadata). Finally, WordPress gets a ready-to-go post and Google Sheets gets the paper trail.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It pulls Google Trends data on a schedule via SerpAPI and selects a topic automatically.
It gathers credible sources using Perplexity and formats the research for writing.
It drafts the article, adds internal links from your Sheets-based post list, and outputs semantic HTML.
It generates slug, title, and meta description, fetches a cover image, and publishes to WordPress.

Most teams save about 3–5 hours per post because research, writing, and uploading are handled.
You publish on a consistent cadence without “content day” chaos.
Posts ship with internal links already in place, so your site structure strengthens over time.
Every URL and target keyword is logged in Google Sheets, which makes refreshing and reporting simple.
You catch emerging search demand earlier, before topics get saturated.

Example: What This Looks Like

Say you publish 3 posts a week. Manually, a typical cycle looks like: 45 minutes of trend/topic digging, about 2 hours writing, about 1 hour formatting in WordPress, 20 minutes adding internal links, and 10 minutes logging details in a sheet. Call it roughly 4 hours per post, or about 12 hours a week. With this workflow, you spend maybe 20 minutes upfront dialing in prompts and the Sheets template, then each run is hands-off while n8n researches, writes, publishes, and logs automatically.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
WordPress for publishing via REST API.
Google Sheets to store links and publishing logs.
SerpAPI key (get it from your SerpAPI dashboard).
Perplexity API key (get it from your Perplexity account settings).
OpenRouter API key (get it from the OpenRouter keys page).

Skill level: Intermediate. You’ll connect a few APIs, map some fields, and test one full run end-to-end.

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

How It Works

A scheduled trigger kicks things off. You set the cadence (daily, weekly, whatever fits), and n8n starts the run automatically without someone needing to remember “content time.”

Trend data is collected and narrowed down. The workflow queries Google Trends through SerpAPI, picks a strong trend pair, then filters for higher-volume terms so you’re not writing for keywords with no demand.

Research and writing happen with guardrails. Perplexity gathers credible sources and fact context, then AI agents draft the article and weave in internal links by looking up your past posts stored in Google Sheets.

Publishing and tracking are automatic. The workflow generates a slug, title, and meta description, fetches a cover image, posts to WordPress, then records the WordPress URL and target keyword back into Sheets.

You can easily modify the publishing frequency to add a human review checkpoint based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Run Trigger

This workflow starts on a schedule and pulls trending topics automatically, so the trigger must be set first.

Add and open Scheduled Run Trigger.
Set the Rule interval to your preferred schedule (this workflow uses the default schedule settings as a placeholder).
Ensure Scheduled Run Trigger is connected to Retrieve Google Trends.

Step 2: Connect Trend Data Sources and Filters

These nodes pull trend data and narrow it down to high-volume candidates.

Open Retrieve Google Trends and set URL to https://serpapi.com/search?engine=google_trends.
In Retrieve Google Trends, set Query Parameters: q to ai agent, geo to US, hl to en, date to {{ $now.minus({ days: 3 }).format('yyyy-MM-dd') }} {{ $now.format('yyyy-MM-dd') }}, and data_type to RELATED_QUERIES.
Credential Required: Connect your httpQueryAuth credentials in Retrieve Google Trends (required by genericCredentialType).
Open Pick Top Trend Pair and set Mode to raw with JSON Output set to the provided expression in the node.
Open Filter High-Volume Terms and confirm JavaScript Code uses $('Retrieve Google Trends') to filter extracted_value > 30.

⚠️ Common Pitfall: If Retrieve Google Trends fails authentication, confirm your SerpAPI key is included in the httpQueryAuth credential.

Step 3: Set Up AI Topic Selection and Research

This stage uses AI to select the best trending topic and gather research sources.

Open Choose Best SEO Topic and ensure it references the trend pair via {{ $('Pick Top Trend Pair').item.json['most-trending']['#1'].toJsonString() }} and {{ $('Pick Top Trend Pair').item.json['most-trending']['#2'].toJsonString() }}.
Credential Required: Connect your openAiApi credentials in Choose Best SEO Topic.
Open Gather Credible Sources and set URL to https://api.perplexity.ai/chat/completions with Method set to POST and JSON Body set to the provided expression.
Credential Required: Connect your httpHeaderAuth credentials in Gather Credible Sources.
Open Format Research Output and confirm the research field is set to {{ $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]) }}.

Tip: If you adjust the Perplexity model or response format in Gather Credible Sources, update the replacement logic in Format Research Output to keep citations aligned.

Step 4: Compose the Blog Draft and Internal Linking

These nodes draft the post and enrich it with internal links from your existing posts.

Open Compose Blog Draft and verify it references {{ $('Choose Best SEO Topic').item.json.message.content }} and {{ $json.research }} in the message content.
Credential Required: Connect your openAiApi credentials in Compose Blog Draft.
Open Retrieve Past Posts and set Document ID to [YOUR_ID] and Sheet Name to gid=0.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Past Posts.
Open Compile Internal Link Data and set Aggregate to aggregateAllItemData with Destination Field Name as previous-posts.
Open Inject Internal SEO Links and verify it uses {{ $('Compose Blog Draft').item.json.message.content }} and {{ $json['previous-posts'].toJsonString().split() }}.
Credential Required: Connect your openAiApi credentials in Inject Internal SEO Links.

Step 5: Build HTML, SEO Metadata, and Cover Image

This stage formats the post, creates SEO metadata, and retrieves a cover image.

Open Build Semantic HTML and ensure it uses {{ $json.message.content }} to generate HTML.
Credential Required: Connect your openAiApi credentials in Build Semantic HTML.
Open Generate SEO Slug and confirm it references {{ $('Inject Internal SEO Links').item.json.message.content }} and {{ $('Choose Best SEO Topic').item.json.message.content }}.
Credential Required: Connect your openAiApi credentials in Generate SEO Slug.
Open Craft Blog Title and confirm it references {{ $('Inject Internal SEO Links').item.json.message.content }} and the primary keyword expression.
Credential Required: Connect your openAiApi credentials in Craft Blog Title.
Open Write Meta Description and confirm it references {{ $('Inject Internal SEO Links').item.json.message.content }} and {{ $('Choose Best SEO Topic').item.json.message.content }}.
Credential Required: Connect your openAiApi credentials in Write Meta Description.
Open Retrieve Cover Image and set URL to https://serpapi.com/search?engine=google_images with q set to {{ $('Choose Best SEO Topic').item.json.message.content }} and gl set to us.
Credential Required: Connect your httpQueryAuth credentials in Retrieve Cover Image (required by genericCredentialType).
Open Save Cover Image Link and set image-url to {{ $json.images_results[1].original }}.

⚠️ Common Pitfall: If Retrieve Cover Image returns no results, adjust the query or image index used in Save Cover Image Link.

Step 6: Configure Publishing and Tracking Outputs

These final nodes publish the post to WordPress and log the result in Google Sheets.

Open Post to WordPress and set Title to {{ $('Craft Blog Title').item.json.message.content }}.
In Post to WordPress, set Slug to {{ $('Generate SEO Slug').item.json.message.content }} and Content to <img src="{{ $json['image-url'] }}" alt="Cover Image"> {{ $('Build Semantic HTML').item.json.message.content }}}.
Confirm Status is set to draft, Author ID to 5, and Categories to 43 in Post to WordPress.
Credential Required: Connect your WordPress credentials in Post to WordPress (this node has no credentials configured).
Open Record Published Entry and set Operation to append.
In Record Published Entry, map Link to {{ $json.link }} and Título to {{ $json.title.raw }}.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Record Published Entry.

Step 7: Test and Activate Your Workflow

Run a full test to confirm content generation, posting, and logging all work end-to-end.

Click Execute Workflow and monitor each node from Scheduled Run Trigger through Record Published Entry.
Verify a draft is created in WordPress with the generated title, slug, cover image, and HTML content from Post to WordPress.
Confirm a new row appears in your Google Sheet from Record Published Entry with valid Link and Título values.
If results are correct, toggle the workflow to Active to enable scheduled publishing.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

SerpAPI credentials can expire or hit plan limits. If trend pulls fail, check your SerpAPI usage dashboard and the key stored in n8n 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 Google Trends automation automation?

About 20 minutes once your API accounts are ready.

Do I need coding skills to automate Google Trends automation?

No. You’ll mostly connect accounts and paste API keys. You might tweak a filter or prompt, but you won’t be writing an app.

Is n8n free to use for this Google Trends 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 SerpAPI, Perplexity, and OpenRouter usage, which usually comes out to a few dollars for a batch of posts depending on length and model choice.

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 Google Trends automation automation for adding a human review before publishing?

Yes, and it’s a smart tweak for most brands. Route the “Build Semantic HTML” output into a WordPress draft instead of publishing, then add an approval checkpoint before the “Post to WordPress” node runs. Common customizations include changing the writing prompts for tone, adjusting the Google Trends filters for your niche, and tightening the internal-link rules so it only links to cornerstone pages.

Why is my WordPress connection failing in this workflow?

Usually it’s permissions or the REST API being blocked. Confirm the WordPress user you connected has rights to publish posts, then check if a security plugin or host firewall is denying REST requests. Also verify the site URL in the WordPress node matches your canonical domain (http vs https matters). If it was working and suddenly stopped, regenerate the application password (or credentials) and update it in n8n.

How many posts can this Google Trends automation automation handle?

A lot, as long as your API limits and WordPress hosting can keep up.

Is this Google Trends automation automation better than using Zapier or Make?

For an end-to-end content pipeline, n8n is usually a better fit because it handles branching logic, AI steps, and multi-stage formatting without turning into an expensive spiderweb of zaps. You can also self-host, which is a big deal once you publish frequently. Zapier or Make can be fine for lightweight “draft → publish” flows, but they get clunky when you add research, internal linking, and structured HTML output. Honestly, the best tool is the one you’ll maintain. Talk to an automation expert if you want a quick recommendation based on your volume and stack.

Set it up once and you stop babysitting your content calendar. The workflow handles the repetitive publishing work so your team can spend time on strategy, offers, and distribution.

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,
"name": "Automated Trend-Based Blog Publisher",
"versionId": null,
"meta": {
"instanceId": "4bd66fd2b4983b36ff82a6181ee1ea166fb8e2e1d9a8955d29e2c5091b8d4d60",
"templateId": null,
"templateCredsSetupCompleted": null
},
"nodes": [
{
"id": "flowpast-topbar-8264",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1115,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "d78d08b5-2307-42cf-915c-ad31d3d6ade1",
"name": "Scheduled Run Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
1015,
125
],
"parameters": {
"rule": {
"interval": [
[]
]
}
},
"typeVersion": 1.2
},
{
"id": "de7e7025-fa2a-42f1-a0b7-ded8f9268d0a",
"name": "Retrieve Google Trends",
"type": "n8n-nodes-base.httpRequest",
"position": [
730,
165
],
"parameters": {
"url": "https://serpapi.com/search?engine=google_trends",
"options": [],
"sendQuery": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpQueryAuth",
"queryParameters": {
"parameters": [
{
"name": "q",
"value": "=ai agent"
},
{
"name": "geo",
"value": "US"
},
{
"name": "hl",
"value": "en"
},
{
"name": "date",
"value": "={{ $now.minus({ days: 3 }).format('yyyy-MM-dd') }} {{ $now.format('yyyy-MM-dd') }}"
},
{
"name": "data_type",
"value": "RELATED_QUERIES"
}
]
}
},
"typeVersion": 4.2
},
{
"id": "468c22d2-13a1-4110-a4bb-de96342c36c0",
"name": "Pick Top Trend Pair",
"type": "n8n-nodes-base.set",
"position": [
540,
135
],
"parameters": {
"mode": "raw",
"options": [],
"jsonOutput": "={\n  \"most-trending\": {\n\n    \"#1\": { \n\n      \"query\":\"{{ $json.related_queries.rising[0].query }}\",\n      \"score\":\"{{ $json.related_queries.rising[0].extracted_value }}\"\n\n    },\n\n\n    \"#2\": { \n\n      \"query\":\"{{ $json.related_queries.rising[1].query }}\",\n      \"score\":\"{{ $json.related_queries.rising[1].extracted_value }}\"\n\n    }\n  }\n}"
},
"typeVersion": 3.4
},
{
"id": "a4a393e5-2802-4986-b088-eeefaa0ee43b",
"name": "Filter High-Volume Terms",
"type": "n8n-nodes-base.code",
"position": [
245,
180
],
"parameters": {
"jsCode": "// Get the top array from your JSON\nconst topItems = $('Retrieve Google Trends').first().json.related_queries.top;\n\n// Filter the items to only include those with extracted_value > 30\nconst filtered = topItems.filter(item => item.extracted_value > 30);\n\n// Map the filtered items to their query values and join them with commas\nconst resultString = filtered.map(item => item.query).join(', ');\n\n// Return the result in a new JSON property\nreturn [{ json: { result: resultString } }];\n"
},
"typeVersion": 2
},
{
"id": "ef2c3a0e-a0e0-4226-950a-e9ffa76d308e",
"name": "Choose Best SEO Topic",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
60,
120
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4",
"cachedResultName": "GPT-4"
},
"options": [],
"messages": {
"values": [
{
"content": "=You are part of a team that creates world class blog posts. Your job is to choose the topic for each blog post. \n\nThe blog posts are posted on the website of a [COMPANY NAME + DESCRIPTION + PRODUCTS + TARGET MARKET]. The blog posts are mainly posted as part of an SEO campaign to get [COMPANY NAME] to rank high for its products and services.\n\nIn this instance, you are given a list of 2 keywords which have been trending the most on Google news search over the past few days. \n\nYour job is to pick one which you think would make for the most relevant blog post with the best SEO outcomes for the client. \n\nThe keywords have two attributes: \n\n1. query: This attribute determines the search query that users have been searching for which is trending. \n\n2. value: This attribute determines what percentage increase the keyword has seen compared to previous periods (i.e. the increase in search volume). \n\nYou must choose one out of the taking into consideration both the relevance of the keyword for [COMPANY NAME's] SEO efforts and the comparative trendiness determined by the value attribute. \n\nOutput the keyword you decided to post a blog on and nothing else. Don't explain your reasoning. Just output the keyword. \n\nThis instance: \n\nKeyword 1:\n{{ $('Pick Top Trend Pair').item.json['most-trending']['#1'].toJsonString() }} \n\nKeyword2: \n{{ $('Pick Top Trend Pair').item.json['most-trending']['#2'].toJsonString() }} "
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "12da6344-e832-46ac-bdd7-4a0f3bb40db0",
"name": "Gather Credible Sources",
"type": "n8n-nodes-base.httpRequest",
"position": [
10,
400
],
"parameters": {
"url": "https://api.perplexity.ai/chat/completions",
"method": "POST",
"options": [],
"jsonBody": "={\n  \"model\": \"sonar-pro\",\n  \"messages\": [\n    {\n      \"role\": \"system\",\n      \"content\": \"Act as a professional news researcher who is capable of finding detailed summaries about a news topic from highly reputable sources.\"\n    },\n    {\n      \"role\": \"user\",\n      \"content\": \" Research the following topic and return everything you can find: '{{ $('Choose Best SEO Topic').item.json.message.content }}' \"\n    }\n  ]\n}\n",
"sendBody": true,
"specifyBody": "json",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth"
},
"credentials": {
"httpHeaderAuth": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.2
},
{
"id": "dbc47254-c260-44aa-86b8-183b68e9d500",
"name": "Format Research Output",
"type": "n8n-nodes-base.set",
"position": [
295,
355
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "23b8e8c4-9191-415a-9661-1b60d413528a",
"name": "research",
"type": "string",
"value": "={{ $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]) }}"
}
]
}
},
"typeVersion": 3.4
},
{
"id": "1ed934d0-921a-4deb-a794-27ea4c1ac8f2",
"name": "Compose Blog Draft",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
535,
415
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4",
"cachedResultName": "GPT-4"
},
"options": [],
"messages": {
"values": [
{
"content": "=You are part of a team that creates world class blog posts for SEO purposes. \n\nEvery week your team posts one blog post on the most trending news in this week of AI. As the copywriter for the blogs, you are provided with the folling information: \n\n- Query: The topic of this weeks blog post. This is the most trending news in the space.\n\n- Other keywords: This is a list of some high search volume keywords in the AI space. The goal is to include some of these into the blog post naturally. This is only optional and dependant on the natural dependancy of this weeks topic to the blog post. Include any of the keywords in the blog, if you can do so naturally without changing the meaning of the blog post.  \n\n\n- Research findings: This is research found from very reputable resources in relation to the topic of the post. Your blog post must be based off this research.\n\n\nGiven the said info, you must write the blog post.\n \nThe blog post must: \n\n- Place the query in the blog title, H1 header and early in the introduction. \n\n- Include all detail in research findings. When including the research points, make sure to also include their source URL so that the copywriter can use them as hyperlinks. (source url for each statement is given in the research findings next to the text)\n\n- Be very detailed. \n\n- Be using tone similar to that of a reporter, invoking curiosity and excitement and thrill in the readers.\n\n- Flow naturally and make sense. \n\n- Be at minimum 1500 to 2000 words long. \n\n- Be suitable for a year 5 reading level. \n\nMake sure to create the entire blog post draft in your first output. Don't stop or cut it short. \n\nYour output must be the blog post and nothing else.\n\nHere are the details of your next blog post project: \n\nQuery: \n{{ $('Choose Best SEO Topic').item.json.message.content }}\n\nDetailed Research: \n{{ $json.research }}\n\nWrite the blog post in perfect spanish.\n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "ce242655-b51c-4ff3-8374-1ac63dc6b2f7",
"name": "Retrieve Past Posts",
"type": "n8n-nodes-base.googleSheets",
"position": [
715,
350
],
"parameters": {
"options": [],
"sheetName": {
"__rl": true,
"mode": "list",
"value": "gid=0",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit#gid=0",
"cachedResultName": "Hoja 1"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit?usp=drivesdk",
"cachedResultName": "CONTROL BLOG WEB"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.5,
"alwaysOutputData": true
},
{
"id": "4209d536-18d9-40f2-98b2-c0854d4cc82a",
"name": "Compile Internal Link Data",
"type": "n8n-nodes-base.aggregate",
"position": [
1015,
405
],
"parameters": {
"options": [],
"aggregate": "aggregateAllItemData",
"destinationFieldName": "previous-posts"
},
"typeVersion": 1
},
{
"id": "d3d3e76f-12fb-4bac-b4af-d61cf2b0c9c3",
"name": "Inject Internal SEO Links",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
965,
575
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "o1-mini-2024-09-12",
"cachedResultName": "O1-MINI-2024-09-12"
},
"options": [],
"messages": {
"values": [
{
"content": "=You are part of a SPANISH team that creats world class blog posts. \n\nYou are in charge of internal linking between blog posts. \n\nFor each new blog post that comes across your desk, your job is to look through previously posted blogs and make atleast 5 internal links. \n\nTo choose the best internal linking opportunities you must: \n\n- Read the previous blog post summaries and look through their keywords. If there is a match where the previous blog post is highly relevant, then this is an internal linking opportunity. \n\n- Do not link if it is not highly relevant. Only make a link if it makes sense and adds value for the reader. \n\nOnce you've found the best linking opportunities, you must update the blog post with the internal links. To do this you must: \n\n- Add the link of the previous blog post at the relevant section of the new blog post. Drop the URL at the place which makes most sense. Later we will hyperlink the URL to the word in the blog post which it is placed next to. So your placing is very important. \n\nMake sure to not delete any existing URLs or change anything about the blog post provided to you. You must only add new internal linking URLs and output the revised blog post. \n\nYour output must be the blog post given to you plus the new urls. Don't remove any info. \n\nDon't return the previous blog posts. Only return the current blog post with the internal links added.\n\nCurrent blog Post: \n{{ $('Compose Blog Draft').item.json.message.content }}\n\nPrevious Blog Posts: \n{{ $json['previous-posts'].toJsonString().split() }}\n\n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "8638519e-a8cb-4259-bb4f-de1e7d13dfda",
"name": "Build Semantic HTML",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
785,
645
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "o1-preview",
"cachedResultName": "O1-PREVIEW"
},
"options": [],
"messages": {
"values": [
{
"content": "=DO NOT OUTPUT ANYTHING OTHER THAN THE CODE. I want you to follow the layout of the template as a guide to generate the WordPress code for a blog post. Here are the rules to follow:\n\nThe blog post should have a title, estimated reading time, key takeaways, table of contents, body, and FAQ in this order.\nMake it engaging by using italics, dot points, quotes, bold, spaces, and sometimes new lines. Never use emojis.\nThe blog post will have some URLs referenced next to certain keyphrases to show where the info came from. You must hyperlink the keyphrase with the provided URL so that the reader can click on the referenced URL. It is critical you get this right.\nWrap the entire content in a container <div> with inline CSS that sets the text color to white (#ffffff), uses a legible font such as Arial, sans-serif, and sets line-height to 1.6.\nEnsure that all non-heading text elements (e.g., paragraphs, list items) have an inline style or embedded style that sets their font size to 20px and color to white (#ffffff) using !important to override theme styles.\nHyperlinks, points in the table of contents, and FAQ questions must be styled in blue (#00c2ff).\nAll headings and subheadings should have an underline implemented via a bottom border in blue (#00c2ff) with appropriate padding.\nPlace a double break (<br><br>) between each section to improve readability.\nDo not output any extra text or mention code tags like HTML''' around the output; just output the HTML code.\nBlog post: \n\n{{ $json.message.content }}\n\nHere's an example of a well formatted output:\n\n<div style=\"color: #ffffff; font-family: Arial, sans-serif; line-height: 1.6;\"> <style> p, .wp-block-paragraph, ul.wp-block-list, li { color: #ffffff !important; font-size: 20px !important; } a { color: #00c2ff !important; } </style> <h1 id=\"h-devin-ai-the-hype-and-reality-of-an-ai-software-engineer\" class=\"wp-block-heading\" style=\"border-bottom: 2px solid #00c2ff; padding-bottom: 5px;\">Devin AI: The Hype and Reality of an AI Software Engineer</h1> <br><br> <p class=\"estimated-reading-time\" style=\"color: #ffffff; font-size: 20px !important;\">Estimated reading time: 5 minutes</p> <br><br> <h2 id=\"h-key-takeaways\" class=\"wp-block-heading\" style=\"border-bottom: 2px solid #00c2ff; padding-bottom: 5px;\"><strong>Key Takeaways</strong></h2> <br><br> <ul class=\"wp-block-list\"> <li><mark style=\"background-color: #ffd966;\"><strong>Devin AI</strong></mark> claims to be the world's first fully autonomous AI software engineer.</li> <br><br> <li>Initial demos and claims have generated significant <mark style=\"background-color: #ffff00;\">hype</mark> and interest.</li> <br><br> <li>Critics argue some capabilities may be exaggerated or misleading.</li> <br><br> <li>Real-world testing reveals both <em>strengths</em> and <em>limitations</em>.</li> <br><br> <li>The true impact on software engineering remains to be seen.</li> </ul> <br><br> <div class=\"wp-block-yoast-seo-table-of-contents yoast-table-of-contents\"> <h2 style=\"color: #ffffff; border-bottom: 2px solid #00c2ff; padding-bottom: 5px;\">Table of contents</h2> <br><br> <ul> <li><a href=\"#h-devin-ai-the-hype-and-reality-of-an-ai-software-engineer\" data-level=\"1\">Devin AI: The Hype and Reality of an AI Software Engineer</a></li> <br><br> <li><a href=\"#h-key-takeaways\" data-level=\"2\">Key Takeaways</a></li> <br><br> <li><a href=\"#h-what-is-devin-ai\" data-level=\"2\">What is Devin AI?</a></li> <br><br> <li><a href=\"#h-the-hype-around-devin-ai\" data-level=\"2\">The Hype Around Devin AI</a></li> <br><br> <li><a href=\"#h-putting-devin-to-the-test\" data-level=\"2\">Putting Devin to the Test</a></li> <br><br> <li><a href=\"#h-the-reality-check\" data-level=\"2\">The Reality Check</a></li> <br><br> <li><a href=\"#h-the-future-of-ai-in-software-development\" data-level=\"2\">The Future of AI in Software Development</a></li> <br><br> <li><a href=\"#h-frequently-asked-questions\" data-level=\"2\">Frequently Asked Questions</a></li> </ul> </div> <br><br> <p>Devin AI has burst onto the tech scene, promising to revolutionize software development as we know it. But does this AI-powered coding assistant live up to the hype? Let's dive into what Devin AI really is, what it can do, and what developers are saying after putting it to the test.</p> <br><br> <!-- Rest of blog post content goes here --> </div>\n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "06cc783c-61c6-4a9a-b323-262ba6fb1c25",
"name": "Generate SEO Slug",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
485,
590
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-mini",
"cachedResultName": "GPT-4O-MINI"
},
"options": [],
"messages": {
"values": [
{
"content": "=Create a slug for the following blog post: \n{{ $('Inject Internal SEO Links').item.json.message.content }}\n\nA slug in a blog post is the part of the URL that comes after the domain name and identifies a specific page. It is typically a short, descriptive phrase that summarizes the content of the post, making it easier for users and search engines to understand what the page is about. For example, in the URL www.example.com/intelligent-agents, the slug is intelligent-agents. A good slug is concise, contains relevant keywords, and avoids unnecessary words to improve readability and SEO. \n\nThe slug must be 4 or 5 words max and must include the primary keyword of the blog post which is {{ $('Choose Best SEO Topic').item.json.message.content }}\n\nYour output must be the slug and nothing else so that I can copy and paste your output and put it at the end of my blog post URL to post it right away. "
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "b205436c-d54d-4feb-b61a-623283be197f",
"name": "Craft Blog Title",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
295,
635
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-2024-11-20",
"cachedResultName": "GPT-4O-2024-11-20"
},
"options": [],
"messages": {
"values": [
{
"content": "=Extract the blog post title from the following blog post: \n{{ $('Inject Internal SEO Links').item.json.message.content }}\n\n\n\nThe blog post title must include the primary keyword '{{ $('Choose Best SEO Topic').item.json.message.content }}' and must inform the users right away of what they can expect from reading the blog post. \n\n- Don't put the output in \"\". The output should just text with no markdown or formatting. \n\nYour output must only be the blog post title and nothing else. "
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "c27126d7-1bd6-4d92-834f-e72fb99051a5",
"name": "Write Meta Description",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
0,
620
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-2024-11-20",
"cachedResultName": "GPT-4O-2024-11-20"
},
"options": [],
"messages": {
"values": [
{
"content": "=Create a good meta description for the following blog post: \n\n{{ $('Inject Internal SEO Links').item.json.message.content }}\n\nA good meta description for a blog post that is SEO-optimized should:\n- Be Concise: Stick to 150-160 characters to ensure the full description displays in search results. \n- Include Keywords: Incorporate primary keywords naturally to improve visibility and relevance to search queries.\n\nPrimary keyword = {{ $('Choose Best SEO Topic').item.json.message.content }}\n\n\n- Provide Value: Clearly describe what the reader will learn or gain by clicking the link. \n\n- Be Engaging: Use persuasive language, such as action verbs or a question, to encourage clicks. \n\n- Align with Content: Ensure the description accurately reflects the blog post to meet user expectations and reduce bounce rates. \n\nYour output must only be the meta description and nothing else. \n"
}
]
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.8
},
{
"id": "056b2d84-3167-41cf-860e-716d32ed6847",
"name": "Retrieve Cover Image",
"type": "n8n-nodes-base.httpRequest",
"position": [
60,
875
],
"parameters": {
"url": "https://serpapi.com/search?engine=google_images",
"options": [],
"sendQuery": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpQueryAuth",
"queryParameters": {
"parameters": [
{
"name": "q",
"value": "={{ $('Choose Best SEO Topic').item.json.message.content }}"
},
{
"name": "gl",
"value": "us"
}
]
}
},
"typeVersion": 4.2
},
{
"id": "e1acf94f-f7af-455d-b9f6-79808d9611a9",
"name": "Save Cover Image Link",
"type": "n8n-nodes-base.set",
"position": [
250,
810
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "1f0541df-05ab-4e3d-a5d8-3904579fc8a9",
"name": "image-url",
"type": "string",
"value": "={{ $json.images_results[1].original }}"
}
]
}
},
"typeVersion": 3.4
},
{
"id": "16721919-87a9-4cb5-b71b-26cc24a68f93",
"name": "Post to WordPress",
"type": "n8n-nodes-base.wordpress",
"position": [
490,
885
],
"parameters": {
"title": "={{ $('Craft Blog Title').item.json.message.content }}",
"additionalFields": {
"slug": "={{ $('Generate SEO Slug').item.json.message.content }}",
"status": "draft",
"sticky": false,
"content": "=<img src=\"{{ $json['image-url'] }}\" alt=\"Cover Image\">\n{{ $('Build Semantic HTML').item.json.message.content }}}",
"authorId": 5,
"categories": [
43
],
"postTemplate": {
"values": []
},
"commentStatus": "closed"
}
},
"typeVersion": 1
},
{
"id": "9298b0b6-c50e-47b7-9150-a25d618118ff",
"name": "Record Published Entry",
"type": "n8n-nodes-base.googleSheets",
"position": [
775,
820
],
"parameters": {
"columns": {
"value": {
"Link": "={{ $json.link }}",
"T\u00edtulo": "={{ $json.title.raw }}"
},
"schema": [
{
"id": "Link",
"type": "string",
"display": true,
"required": false,
"displayName": "Link",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "T\u00edtulo",
"type": "string",
"display": true,
"required": false,
"displayName": "T\u00edtulo",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Transcripci\u00f3n",
"type": "string",
"display": true,
"required": false,
"displayName": "Transcripci\u00f3n",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Estado",
"type": "string",
"display": true,
"required": false,
"displayName": "Estado",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "HTML",
"type": "string",
"display": true,
"required": false,
"displayName": "HTML",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "gid=0",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit#gid=0",
"cachedResultName": "Hoja 1"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit?usp=drivesdk",
"cachedResultName": "VIDEO TRANSCRIPT PARA BLOG - LA TRIBU DIVISUAL"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.5
}
],
"pinData": [],
"connections": {
"Generate SEO Slug": {
"main": [
[
{
"node": "Craft Blog Title",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Run Trigger": {
"main": [
[
{
"node": "Retrieve Google Trends",
"type": "main",
"index": 0
}
]
]
},
"Retrieve Cover Image": {
"main": [
[
{
"node": "Save Cover Image Link",
"type": "main",
"index": 0
}
]
]
},
"Retrieve Google Trends": {
"main": [
[
{
"node": "Pick Top Trend Pair",
"type": "main",
"index": 0
}
]
]
},
"Compose Blog Draft": {
"main": [
[
{
"node": "Retrieve Past Posts",
"type": "main",
"index": 0
}
]
]
},
"Retrieve Past Posts": {
"main": [
[
{
"node": "Compile Internal Link Data",
"type": "main",
"index": 0
}
]
]
},
"Craft Blog Title": {
"main": [
[
{
"node": "Write Meta Description",
"type": "main",
"index": 0
}
]
]
},
"Pick Top Trend Pair": {
"main": [
[
{
"node": "Filter High-Volume Terms",
"type": "main",
"index": 0
}
]
]
},
"Post to WordPress": {
"main": [
[
{
"node": "Record Published Entry",
"type": "main",
"index": 0
}
]
]
},
"Choose Best SEO Topic": {
"main": [
[
{
"node": "Gather Credible Sources",
"type": "main",
"index": 0
}
]
]
},
"Save Cover Image Link": {
"main": [
[
{
"node": "Post to WordPress",
"type": "main",
"index": 0
}
]
]
},
"Build Semantic HTML": {
"main": [
[
{
"node": "Generate SEO Slug",
"type": "main",
"index": 0
}
]
]
},
"Format Research Output": {
"main": [
[
{
"node": "Compose Blog Draft",
"type": "main",
"index": 0
}
]
]
},
"Write Meta Description": {
"main": [
[
{
"node": "Retrieve Cover Image",
"type": "main",
"index": 0
}
]
]
},
"Inject Internal SEO Links": {
"main": [
[
{
"node": "Build Semantic HTML",
"type": "main",
"index": 0
}
]
]
},
"Gather Credible Sources": {
"main": [
[
{
"node": "Format Research Output",
"type": "main",
"index": 0
}
]
]
},
"Filter High-Volume Terms": {
"main": [
[
{
"node": "Choose Best SEO Topic",
"type": "main",
"index": 0
}
]
]
},
"Compile Internal Link Data": {
"main": [
[
{
"node": "Inject Internal SEO Links",
"type": "main",
"index": 0
}
]
]
}
}
}