HumationHuman + Automation
Back to Catalog

Automate blog engagement with GPT-5 generated comments for WordPress

Ali KhosravaniAli Khosravani
421 views
2/3/2026
AirtableOrdersWebhookShopifyData Sync
Official Page

This workflow automatically generates realistic comments for your WordPress articles using AI. It makes your blog look more active, improves engagement, and can even support SEO by adding keyword-relevant comments.

How It Works

Fetches all published blog posts from your WordPress site via the REST API.

Builds a tailored AI prompt using the article’s title, excerpt, and content.

Uses OpenAI to generate a short, natural-sounding comment (some positive, some neutral, some longer, some shorter).

Assigns a random commenter name and email.

Posts the generated comment back to WordPress.

Requirements

  1. n8n version: 1.49.0 or later (recommended).
  2. Active OpenAI API key.
  3. WordPress site with REST API enabled.
  4. WordPress API credentials (username + application password).

Setup Instructions

Import this workflow into n8n.

Add your credentials in n8n > Credentials:

OpenAI API (API key).

WordPress API (username + application password).

Replace the sample URL https://example.com with your own WordPress site URL.

Execute manually or schedule it to run periodically.

Categories

AI & Machine Learning

WordPress

Content Marketing

Engagement

Tags

ai, openai, wordpress, comments, automation, engagement, n8n

Automate Blog Engagement with GPT-5 Generated Comments for WordPress

This n8n workflow simplifies and automates the process of generating and posting engaging comments on your WordPress blog posts using OpenAI's powerful language models. It's designed to help you increase interaction and keep your content fresh with minimal manual effort.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: The workflow is initiated manually, allowing you to control when the comment generation process begins.
  2. Edit Fields (Set): This node is used to define or modify data within the workflow. While the specific fields are not detailed in the JSON, it's typically used to set variables, such as the blog post URL, article content, or parameters for the AI model.
  3. OpenAI: This is the core of the workflow. It leverages the OpenAI API to generate a comment. This node would typically receive the blog post content (or a summary) and a prompt to create a relevant and engaging comment.
  4. HTTP Request: This node is responsible for posting the generated comment to your WordPress blog. It would be configured to interact with the WordPress API, sending the comment content, author, and associated post ID.
  5. Sticky Note: A sticky note is included, likely for documentation or internal notes within the workflow, to provide context or instructions for users.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: An API key from OpenAI with access to their language models (e.g., GPT-3.5, GPT-4, or as hinted by the directory name, potentially GPT-5 if available).
  • WordPress Website: A WordPress website where you want to post comments.
  • WordPress API Access: Ensure your WordPress site has the REST API enabled and that you have the necessary credentials (e.g., application passwords for a user with comment posting permissions) to interact with it via the HTTP Request node.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI: Add your OpenAI API Key as a credential in n8n and select it in the OpenAI node.
    • WordPress: Configure the HTTP Request node with your WordPress site's API endpoint and authentication details (e.g., Basic Auth with application password, or OAuth if applicable).
  3. Customize the "Edit Fields" Node: Adjust the "Edit Fields" (Set) node to provide the necessary input for the OpenAI node. This might include:
    • The URL of the blog post.
    • The content of the blog post (fetched from a previous step or manually provided).
    • Any specific instructions or personas for the AI-generated comment.
  4. Customize the "OpenAI" Node: Refine the prompt within the OpenAI node to guide the AI in generating comments that match your desired tone, length, and style.
  5. Customize the "HTTP Request" Node: Ensure the HTTP Request node is correctly configured to send a POST request to your WordPress comments API endpoint, including the post_id, author_name, author_email, and content (the AI-generated comment) in the request body.
  6. Execute the Workflow: Click the "Execute workflow" button on the "Manual Trigger" node to run the workflow.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

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

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247