HumationHuman + Automation
Back to Catalog

Automated blog content generation with GPT-4o from Google Trends to WordPress

IranServer.comIranServer.com
1004 views
2/3/2026
AISQLOpenAIAutomationDatabase
Official Page

Automated Blog Content Generation from Google Trends to WordPress

This n8n workflow automatically generates SEO-friendly blog content based on trending topics from Google Trends and publishes it to WordPress. Perfect for content creators, bloggers, and digital marketers who want to stay on top of trending topics with minimal manual effort.

Who's it for

  • Content creators who need fresh, trending topic ideas
  • Bloggers looking to automate their content pipeline
  • Digital marketers wanting to capitalize on trending searches
  • WordPress site owners seeking automated content generation
  • SEO professionals who want to target trending keywords

How it works

The workflow operates on a scheduled basis (daily at 8:45 PM by default) and follows this process:

  1. Trend Discovery: Fetches the latest trending searches from Google Trends for a specific country (Iran by default)
  2. Content Research: Performs Google searches on the top 3 trending topics to gather detailed information
  3. AI Content Generation: Uses OpenAI's GPT-4o model to create SEO-friendly blog posts based on the trending topics and search results
  4. Structured Output: Ensures the generated content has proper title and content structure
  5. Auto-Publishing: Automatically creates draft posts in WordPress

The AI is specifically prompted to create engaging, SEO-optimized content without revealing the automated sources, ensuring natural-sounding blog posts.

How to set up

  1. Install required community node:

    • n8n-nodes-serpapi for Google Trends and Search functionality

  2. Configure credentials:

    • SerpApi: Sign up at serpapi.com and add your API key
    • OpenAI: Add your OpenAI API key for GPT-4o access
    • WordPress: Configure your WordPress site credentials

  3. Customize the country code: Change the "Country" field in the "Edit Fields" node (currently set to "IR" for Iran)

  4. Adjust the schedule: Modify the "Schedule Trigger" to run at your preferred time

  5. Test the workflow: Run it manually first to ensure all connections work properly

Requirements

  • SerpApi account (for Google Trends and Search data)
  • OpenAI API access (for content generation using GPT-4o)
  • WordPress site with API access enabled

How to customize the workflow

  • Change target country: Modify the country code in the "Edit Fields" node to target different regions
  • Adjust content quantity: Change the limit in the "Limit" node to process more or fewer trending topics
  • Modify AI prompt: Edit the prompt in the "Basic LLM Chain" node to change writing style or focus
  • Schedule frequency: Adjust the "Schedule Trigger" for different posting frequencies
  • Content status: Change from "draft" to "publish" in the WordPress node for immediate publishing
  • Add content filtering: Insert additional nodes to filter topics by category or keywords

Automated Blog Content Generation with GPT-4o from Google Trends to WordPress

This n8n workflow automates the process of generating blog post content based on trending topics and publishing it to WordPress. It leverages the power of Large Language Models (LLMs) to create engaging articles, streamlining content creation from ideation to publication.

What it does

This workflow simplifies and automates the following steps:

  1. Triggers on a Schedule: The workflow starts at predefined intervals (e.g., daily, weekly) to check for new content opportunities.
  2. Sets Initial Data: An "Edit Fields (Set)" node is present, which can be configured to initialize or transform data, potentially for defining the scope of content generation or setting parameters for the LLM.
  3. Limits Items: A "Limit" node is included, which can be used to control the number of items processed in subsequent steps, useful for managing API call limits or focusing on a specific number of topics.
  4. Generates Content with LLM Chain: A "Basic LLM Chain" node, powered by an "OpenAI Chat Model", is used to generate blog post content. This chain likely takes a prompt (which could be dynamically generated from trending topics, though not explicitly shown in this JSON) and produces an article.
  5. Parses Structured Output: A "Structured Output Parser" is used to extract specific data fields from the LLM's response, ensuring the generated content (e.g., title, body, tags) is in a structured format suitable for publishing.
  6. Executes Custom Code: A "Code" node is available for executing custom JavaScript logic. This could be used for further data manipulation, validation, or integration with other services not directly supported by n8n nodes.
  7. Publishes to WordPress: The final step publishes the generated and processed content as a new post on a WordPress site.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • OpenAI API Key: For the "OpenAI Chat Model" to generate content. This needs to be configured as an n8n credential.
  • WordPress Account: Access to a WordPress site with appropriate credentials (username, password, or application password) configured in n8n.
  • Potential Google Trends Integration: While not explicitly shown in the provided JSON, the directory name suggests an integration with Google Trends. If this is the case, you might need a Google API key or a custom node/script to fetch trending topics.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI API Key as an n8n credential.
    • Set up your WordPress credentials (e.g., API Key, Username/Password) as an n8n credential.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency for content generation (e.g., daily, weekly).
    • Edit Fields (Set): Configure this node to define any initial data or parameters for your content generation. This is where you might inject trending topics if you're fetching them from an external source.
    • Basic LLM Chain / OpenAI Chat Model: Customize the prompt to guide the AI in generating the desired blog post style, length, and content.
    • Structured Output Parser: Ensure the schema defined in this node matches the expected output format from your LLM chain.
    • Code: If you need any custom logic, modify the JavaScript in this node.
    • WordPress: Configure the WordPress node to specify the post status (e.g., 'draft', 'publish'), categories, tags, and map the generated content fields (title, body) to the WordPress post fields.
  4. Activate the Workflow: Once configured, activate the workflow to start automating your blog content generation.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942