HumationHuman + Automation
Back to Catalog

Content farming - : AI-powered blog automation for WordPress

Jay Emp0Jay Emp0
30205 views
2/3/2026
AIAirtableAutomationSummarizationGmail
Official Page

==🔥 Upgrade to V4==

We’ve released Version 4 of our AI Powered Blog Automation workflow. We heard your complains and made a complete redesign built for serious content creators.

ChatGPT 5, Inbound Links, Verified Outbound Links,YOAST seo integration, Company profile, higher SEO ranking, banner images using companys mascot, FAQ sections and conclusions, 35% cost reduction,

📝 Read the New Articles published by Content Farming v4

🛒 View the updated and improved v4 workflow

Content Farming V2

AI Powered Blog Automation for WordPress

This workflow automatically generates and publishes 10 blog posts per day to a WordPress site. It collects tech-related news articles, filters and analyzes them for relevance, expands them with research, generates SEO-optimized long-form articles using AI, creates a matching image using Leonardo AI, and publishes them via the WordPress REST API. Every step is tracked and stored in MongoDB for reference and performance tracking.

You can see the demo results for the AI based articles here: Emp0 Articles

Screenshot 20250625 010731.png

How it works

  1. A scheduler runs daily to fetch the latest news from RSS feeds including BBC, TechCrunch, Wired, MIT Tech Review, HackerNoon, and others.
  2. The RSS data is normalized and filtered to include only articles published within the past 24 hours.
  3. Each article is passed through an OpenAI-powered classifier to check for relevance to predefined user topics like AI, robotics, or tech policy.
  4. Relevant articles are then aggregated, researched, and summarized with supporting sources and citations.
  5. An AI agent generates five long-tail SEO blog title ideas, ranks them by uniqueness and performance score, and selects the top one.
  6. A blog outline is created including H1 and H2 headers, keyword targeting, content structure, and featured snippet optimization.
  7. A full-length article (1000 to 1500 words) is generated based on the outline, with analogies, citations, examples, and keyword density maintained.
  8. SEO metadata is produced including meta title, description, image alt text, slug, and a readability audit.
  9. An AI-generated image is created based on the blog theme using Leonardo AI, enhanced for emotional storytelling and visual consistency.
  10. The blog article, metadata, and image are uploaded to WordPress as a draft, the image is attached, Yoast SEO metadata is set, and the article is published.

All outputs including article versions, metadata, generation steps, and final blog URLs are stored in MongoDB to allow for future analytics and feedback.

Requirements

To run this project, you need accounts and API access for the following:

| Tool | Purpose | Notes | |--------------|------------------------------------------------------------------|-----------------------------------------------------------------------| | OpenAI | Used for blog classification, generation, summarization, SEO | Around $0.20 per day, using GPT-4o-mini. Estimated monthly: $6 | | MongoDB | Stores data flexibly including drafts, titles, metadata, logs | Free tier on MongoDB Atlas offers 512 MB, enough for 64,000 articles | | Leonardo AI | Generates featured images for blog articles | $9 for 3500 credits, $5 monthly top-up needed for 300 images | | WordPress | Final publishing platform via REST API | Hosted on Hostinger for $15/year including domain |

Setup Instructions

  1. Import the provided JSON file into your n8n instance.
  2. Configure these credentials in n8n:
    • OpenAI API key
    • MongoDB Atlas connection string
    • HTTP Header Auth for Leonardo AI
    • WordPress REST API credentials
  3. Modify the classifier and prompt nodes to reflect your preferred content themes.
  4. Adjust scheduler nodes if you want to change post frequency or publishing times.
  5. Run the n8n instance continuously using Docker, PM2, or hosted automation platform.

Cost Estimate

| Component | Daily Usage | Monthly Cost Estimate | |---------------|------------------------------|------------------------| | OpenAI | 10 posts per day | ~$6 | | Leonardo AI | 10 images per day (15 credits each) | ~$14 (9 base + 5 top-up) | | MongoDB | Free up to 512 MB | $0 | | WordPress | Hosting and domain | ~$1.25 | | Total | | ~$21/month |

Observations and Learnings

This system can scale daily article publishing with zero manual effort. However, current limitations include inconsistent blog length and occasional coherence issues. To address this, I plan to build a feedback loop within the workflow:

  • An SEO Commentator Agent will assess keyword strength, structure, and discoverability.
  • An Editor-in-Chief Agent will review tone, clarity, and narrative structure.
  • Both agents will loop back suggestions to the content generator, improving each draft until it meets human-level standards.

The final goal is to consistently produce high-quality, readable, SEO-optimized content that is indistinguishable from human writing.

AI-Powered Blog Automation for WordPress

This n8n workflow automates the process of generating and publishing blog posts to WordPress, leveraging AI to create content from RSS feed articles. It checks for new articles, uses an AI agent to summarize and generate a blog post, and then publishes it to WordPress.

What it does

  1. Triggers on a Schedule: The workflow starts on a predefined schedule (e.g., daily, hourly).
  2. Reads RSS Feed: It fetches the latest articles from a specified RSS feed.
  3. Filters Existing Posts: It checks a MongoDB database to ensure that only new articles (not previously processed) are considered.
  4. Processes Articles in Batches: Each new article is processed individually to manage AI API calls efficiently.
  5. Generates Blog Content with AI:
    • It extracts the full HTML content of the article using an HTTP Request.
    • It then uses an AI Agent (powered by an OpenAI Chat Model) to summarize the article and generate a full blog post, including title, content, and tags.
    • A Structured Output Parser ensures the AI output is correctly formatted.
  6. Classifies Content with AI: An AI Text Classifier categorizes the generated content, likely for assigning appropriate WordPress categories or tags.
  7. Publishes to WordPress: The generated and classified blog post is then published to a WordPress site.
  8. Logs Processed Articles: The URL of the published article is saved to a MongoDB database to prevent duplicate processing.
  9. Includes a Wait Step: A short delay is introduced between publishing posts, potentially to avoid overwhelming the WordPress API or to simulate human-like publishing frequency.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • WordPress Account: Access to a WordPress site with API credentials.
  • OpenAI API Key: An API key for OpenAI to power the AI Agent and Text Classifier.
  • MongoDB Database: Access to a MongoDB database for storing processed article URLs.
  • RSS Feed URL: The URL of the RSS feed you wish to monitor.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • WordPress: Set up your WordPress credentials (API Key/Application Password and URL).
    • OpenAI: Configure your OpenAI API key credential.
    • MongoDB: Set up your MongoDB credentials (connection string, database name, and collection name).
  3. Configure RSS Read Node (Node 37):
    • Enter the URL of the RSS feed you want to monitor.
  4. Configure MongoDB Nodes (Node 59):
    • Ensure the "MongoDB" node is configured to connect to your database and collection where processed article URLs will be stored.
  5. Configure AI Nodes (Nodes 1119, 1153, 1179, 1265):
    • Verify that the "AI Agent", "OpenAI Chat Model", "Structured Output Parser", and "Text Classifier" nodes are correctly linked to your OpenAI credential.
    • You may need to adjust the AI prompts within the "AI Agent" node to fine-tune the content generation to your specific needs.
  6. Configure WordPress Node (Node 118):
    • Ensure the "WordPress" node is configured to publish posts to your desired WordPress site.
  7. Activate the workflow: Once configured, activate the workflow. It will run automatically based on the schedule defined in the "Schedule Trigger" node (Node 839).
  8. Adjust Schedule (Optional): Modify the "Schedule Trigger" node (Node 839) to set your preferred frequency for checking the RSS feed and publishing new content.
  9. Adjust Wait Time (Optional): Modify the "Wait" node (Node 514) to change the delay between publishing posts.

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

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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