🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

Google Trends to WordPress, drafts ready to review

Lisa Granqvist Partner Workflow Automation Expert

Your blog calendar looks fine on paper. Then the week gets busy, trending topics move on, and you are stuck choosing between “publish something” and “publish something good.” Meanwhile, the same steps repeat every time: find a keyword, outline, write, grab an image, upload, format, and hope you didn’t miss basic SEO fields.

Content managers feel it when the backlog goes stale. Solo founders feel it when writing steals from selling. And marketing teams at small agencies feel it when client blogs need fresh drafts weekly. This Google Trends automation turns trends into WordPress drafts you can review, which means consistency without living in Google tabs.

Below, you’ll see exactly what the workflow does, what you get out of it, and how to make it fit your niche and brand voice without overengineering anything.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Trends to WordPress, drafts ready to review

The Problem: Trending topics don’t wait for your writing time

Staying consistent with content is hard enough. Staying consistent while chasing trends is worse. You find a topic on Google Trends, then you copy it into a doc, then a sheet, then you try to shape it into a post that won’t embarrass your brand. Images turn into another time sink: search, download, resize, upload, and then you still need alt text and a featured image set correctly. A single missed detail can derail the whole “quick draft” idea, so drafts don’t ship and the calendar slips.

It adds up fast. Here’s where it breaks down in real life.

  • You end up spending about an hour just to get from “trend” to “draft,” and that’s before edits.
  • Keywords get tracked inconsistently, so you can’t tell what was used, what’s pending, or what performed.
  • Images get treated as an afterthought, which leads to unbranded visuals and missing SEO metadata.
  • Publishing becomes an all-or-nothing task, so busy weeks quietly become zero-post weeks.

The Solution: Turn Google Trends into branded WordPress drafts

This workflow runs on a schedule and pulls trending search terms from Google Trends, then turns one of those terms into a clean WordPress draft you can review. First, it fetches the Trends feed, converts the XML into JSON, and filters the list down to terms that match what you actually want to write about. Those keywords are logged in Google Sheets, so you have a lightweight content queue and you can see what’s already been used. From there, the workflow selects a keyword, asks OpenAI to generate structured blog content, and then cleans the output so it’s formatted and usable. Finally, it finds a matching stock image on Pexels, applies a watermark for branding, uploads the media to WordPress, sets it as the featured image, and saves the post as a draft.

The workflow starts with a scheduled trigger and a few “primary settings” you control (like region and filtering behavior). Then it cycles through trend keywords, picks one at random, generates the post, and marks that keyword as done in your Google Sheet so it doesn’t get reused accidentally. WordPress gets a draft with text, featured image, and updated media details, ready for your final human review.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you want 5 trend-based drafts per week. Manually, a typical cycle is roughly 20 minutes to find and vet a topic, about an hour to draft, and another 20 minutes to find and prep an image, so call it about 2 hours per post (around 10 hours weekly). With this workflow, you spend maybe 10 minutes total per draft doing quick review and edits because the keyword, text, and featured image are already waiting in WordPress. That’s most of a workday back each week.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Sheets for keyword queue tracking.
  • WordPress to create drafts via API access.
  • OpenAI API key (get it from your OpenAI dashboard).
  • Pexels API key (get it from the Pexels API page).

Skill level: Intermediate. You’ll connect accounts, add API keys, and verify WordPress permissions, but you won’t be writing code unless you want deeper filtering.

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

How It Works

A scheduled run kicks things off. n8n starts on a timer (daily, hourly, whatever you choose) and loads your primary settings, like the Trends region you care about.

Google Trends gets fetched and filtered. The workflow pulls the Trends feed via HTTP Request, parses the XML into JSON, then filters terms using a small logic step so you don’t clutter your pipeline with irrelevant topics.

Keywords are tracked in Google Sheets. New terms are appended or updated in your sheet, then the workflow selects a single keyword to work on and marks it done after the draft is generated.

OpenAI creates the draft and WordPress receives it. The AI agent generates structured content, a cleanup step removes weird formatting, and WordPress gets a fresh draft. After publishing the draft, the workflow searches Pexels, applies your watermark, uploads the image, sets it as featured, and updates media details for SEO.

You can easily modify the keyword filtering to focus on your niche, or adjust the prompt to match your brand voice and formatting rules. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

This workflow starts on a recurring schedule and then initializes global settings for trend filtering.

  1. Open Scheduled Automation Trigger and set the interval rule to run every 25 minutes.
  2. Connect Scheduled Automation Trigger to Primary Settings exactly as shown in the flow.
  3. In Primary Settings, set min_traffic to 500 to filter low-traffic trends.

Step 2: Fetch and Filter Google Trends Data

These nodes pull the trending RSS feed, parse it, and filter by traffic threshold before batching.

  1. In Google Trends Fetch, set URL to https://trends.google.it/trending/rss and keep Send Query enabled.
  2. In Google Trends Fetch, add a query parameter geo with value US.
  3. In XML Parse, keep normalize as false and explicitArray as false.
  4. In Filter Trend Keywords, keep the JavaScript as provided, which reads $('Primary Settings').first().json.min_traffic and filters the RSS items.
  5. Connect Filter Trend Keywords to Batch Iterate Records to begin iterative processing.

Step 3: Connect Google Sheets for Keyword Tracking

Google Sheets stores trend keywords and tracks processing status. This workflow uses multiple Sheets nodes, so connect credentials once and apply them to all Sheets nodes.

  1. Open Retrieve Sheet Rows and select the document Primary Sheet with sheet Keyword Tracker.
  2. In Retrieve Sheet Rows, set the filter to Status equals processing.
  3. Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Sheet Rows, Append/Update Sheet Row, and Mark Sheet Row Done.
  4. In Append/Update Sheet Row, confirm the field mappings use expressions like {{ $json.trending_keyword }} and {{Math.floor(Math.random()*999999999)}}.
  5. In Mark Sheet Row Done, keep operation set to update and ensure Status is set to done with Keyword mapped to {{ $('Select Random Keyword').item.json.Keyword }}.

Step 4: Set Up AI Content Generation

The AI agent creates the article JSON, which is parsed and later cleaned before publishing.

  1. In Select Random Keyword, keep the JavaScript logic that filters for Status === "processing" and randomly selects one item.
  2. In AI Content Agent, keep the Text prompt and ensure expressions are preserved, such as {{ $json.Keyword }} and {{ $json['Example Title 1'] }}.
  3. Open OpenAI Chat Engine and select model gpt-4.1-mini.
  4. Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
  5. Open Structured Output Reader and confirm the JSON schema example matches the expected fields.
  6. Note: Structured Output Reader is an AI sub-node—add credentials on OpenAI Chat Engine, not on Structured Output Reader.

Step 5: Configure Media and WordPress Publishing

This stage fetches a Pexels image, applies a watermark, uploads media, and publishes a WordPress draft with a featured image.

  1. In Pexels Image Lookup, keep the request URL expression https://api.pexels.com/v1/search?query={{ encodeURIComponent($('AI Content Agent').item.json.output.images_query)}}&per_page=1.
  2. Credential Required: Connect your httpHeaderAuth credentials in Pexels Image Lookup.
  3. In Apply Image Watermark, keep URL as https://quickchart.io/watermark and set mainImageUrl to {{ $('Pexels Image Lookup').item.json.photos[0].src.landscape }}.
  4. In Apply Image Watermark, update markImageUrl to your own watermark file, replacing [CONFIGURE_YOUR_API_KEY].
  5. In Upload Media Asset, keep URL as https://clipmint.pro/wp-json/wp/v2/media and Content-Disposition as attachment; filename="{{ $('AI Content Agent').item.json.output.images_query }}.jpg".
  6. Credential Required: Connect your wordpressApi credentials in Publish WordPress Draft, Upload Media Asset, Assign Featured Image, and Update Media Details.
  7. In Publish WordPress Draft, set Title to {{ $('AI Content Agent').item.json.output.title }}, Status to draft, and Content to {{ $json.output.content }}.
  8. In Assign Featured Image, keep the post URL expression https://clipmint.pro/wp-json/wp/v2/posts/{{ $('Publish WordPress Draft').item.json.id }} and set featured_media to {{ $json.id }}.
  9. In Update Media Details, keep the JSON body mapping for title, alt_text, and description using AI outputs.

⚠️ Common Pitfall: The watermark URL contains a placeholder ([CONFIGURE_YOUR_API_KEY]). Replace it with your actual asset path to avoid failed watermarking requests.

Step 6: Test and Activate Your Workflow

Run a manual test to verify data pulls, AI generation, and WordPress drafts before activating the schedule.

  1. Click Execute Workflow to run a manual test from Scheduled Automation Trigger.
  2. Confirm Append/Update Sheet Row adds trend keywords and Retrieve Sheet Rows returns rows with Status set to processing.
  3. Verify AI Content Agent returns structured JSON that Structured Output Reader can parse.
  4. Check WordPress for a new draft created by Publish WordPress Draft and verify the featured image is set by Assign Featured Image.
  5. When everything succeeds, toggle the workflow to Active so Scheduled Automation Trigger runs every 25 minutes.
🔒

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 user role capabilities) 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 45 minutes if you already have API keys and WordPress access.

Do I need coding skills to automate Google Trends automation?

No. You’ll mostly paste API keys and connect accounts in n8n. The only “code-like” parts are optional filters you can leave as-is.

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 OpenAI API costs (usually a few cents per draft, depending on length) and Pexels (free, but requires an API key).

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 workflow for a specific niche and tone?

Yes, and you should. Update the prompt inside the AI Content Agent to include your audience, examples of your voice, and any formatting rules (like headings, FAQs, or a standard intro). Many teams also tweak the Filter Trend Keywords logic to exclude off-brand topics, and adjust the Pexels query terms so images match your style better.

Why is my WordPress connection failing in this workflow?

Usually it’s an application password issue or the WordPress user doesn’t have permission to create posts and upload media. Regenerate the application password, confirm the site URL is correct (including https), and then re-test the WordPress node. If it fails only on media steps, check that your hosting or security plugin isn’t blocking REST API media uploads. Rate limiting can also show up if you run the schedule too aggressively.

How many drafts can this Google Trends automation automation handle?

On n8n Cloud, it depends on your plan’s monthly executions, and on self-hosting it mostly depends on your server. Practically, most small sites run this once or a few times per day and stay well within limits. If you batch lots of keywords at once, expect OpenAI and WordPress API calls to be the real throttle points.

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

It can be, especially if you want branching logic, cleanup steps, and tighter control over how content and media get handled. n8n is also easier to scale cheaply because self-hosting removes the “every step costs more” feeling once volume increases. Zapier or Make are fine for simpler flows, but this one benefits from having code steps, structured output parsing, and multiple HTTP requests in a single run. If you’re unsure, map your desired output first (draft quality, image handling, tracking) and then pick the tool that won’t force compromises. Talk to an automation expert and we’ll help you choose quickly.

Once this is running, drafts show up even when you’re busy. Honestly, that’s the whole win: less scrambling, more publishing, and a calendar you can trust.

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.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal