HumationHuman + Automation
Back to Catalog

Automate SEO blog creation from trends using Gemini AI, Apify, and Google Docs

Parth PansuriyaParth Pansuriya
343 views
2/3/2026
emailIMAPfilesautomationattachments
Official Page

Automate SEO Blog Creation with Apify + Google Docs + KIE AI’s Nano Banana API

Who’s it for

For content creators, SEO specialists, and digital marketers who want to automatically generate SEO-optimized blog posts from trending topics — no manual writing or formatting required.

How it works / What it does

This workflow turns trending searches into fully structured blog posts using AI:

  1. Fetch trending topics from India (or any country) using Apify’s Google Trends scraper.
  2. Generate a SEO-optimized blog post with title, meta description, headings, and long-form content using Gemini AI.
  3. Refine the System Message (optional) with Gemini AI for better readability and engagement.
  4. Create a custom blog image using KIE AI’s Nano Banana API based on the blog title.
  5. Automatically insert all content and images into a Google Doc, ready for publishing.

How to set up

  1. Add your Apify API token in the Google Trends node.
  2. Configure Google Docs OAuth2 credentials for the document update node.
  3. Add your KIE AI Nano Banana API token for image generation.
  4. Schedule the Daily Trigger to your preferred time (default is 8 AM).

Requirements

  1. Apify API token (for trending search scraping)
  2. Google account with Docs access
  3. KIE AI Nano Banana API token

How to customize the workflow

  1. Change country or timeframe for trending searches.
  2. Update the AI prompt for tone, length, or style of the blog.
  3. Change the Google Doc ID to insert content into a different document.
  4. Adjust image generation settings (size, style) in the KIE AI node.

Automate SEO Blog Creation from Trends using Gemini AI, Apify, and Google Docs

This n8n workflow automates the process of generating SEO-optimized blog posts based on trending topics. It leverages Apify to find trending keywords, uses Google Gemini AI to generate blog content, and then outputs the content for further use (e.g., publishing to Google Docs, CMS, etc.).

What it does

This workflow streamlines the content creation process by:

  1. Scheduling Execution: Runs on a predefined schedule to regularly check for new trends.
  2. Fetching Trending Keywords: Makes an HTTP request to an external service (likely Apify) to retrieve trending SEO keywords.
  3. Filtering Keywords: Checks if any keywords were successfully retrieved. If no keywords are found, the workflow stops.
  4. Preparing AI Input: If keywords are found, it prepares the data for the AI agent, likely extracting the most relevant keywords.
  5. Generating Blog Content with AI: Uses a Google Gemini Chat Model within an AI Agent to generate blog post content based on the trending keywords.
  6. Parsing AI Output: Processes the AI-generated content using a Structured Output Parser to extract specific elements (e.g., title, headings, body).
  7. Waiting (Optional Delay): Includes an optional delay, which might be useful for rate limiting or staggering content generation.
  8. Outputting Processed Data: Prepares the final blog post data for subsequent actions (e.g., writing to a Google Doc, publishing to a CMS).

Prerequisites/Requirements

To use this workflow, you will need:

  • Apify Account: To access trending SEO keywords via an HTTP request.
  • Google Gemini API Key: For the Google Gemini Chat Model to generate content.
  • n8n Instance: Where you will import and run this workflow.

Setup/Usage

  1. Import the workflow: Download the JSON file and import it into your n8n instance.
  2. Configure Credentials:
    • HTTP Request (Node 19): Update the HTTP Request node with your Apify API endpoint and any necessary authentication to fetch trending keywords.
    • Google Gemini Chat Model (Node 1262): Configure your Google Gemini API key as a credential in n8n and select it for this node.
  3. Adjust Schedule Trigger (Node 839): Modify the "Schedule Trigger" node to define how often you want the workflow to run (e.g., daily, weekly).
  4. Review AI Agent (Node 1119): Examine the "AI Agent" node to understand the prompts and instructions given to the Google Gemini model. Adjust as needed for your specific content requirements.
  5. Review Structured Output Parser (Node 1179): Ensure the "Structured Output Parser" node is correctly configured to extract the desired fields from the AI's output.
  6. Extend the workflow: After the "Edit Fields" node (Node 38), you can add additional nodes to:
    • Write the generated content to a Google Doc.
    • Publish to a CMS (e.g., WordPress, Webflow).
    • Send notifications (e.g., Slack, Email) about new posts.
  7. Activate the workflow: Once configured, activate the workflow to start automating your SEO blog creation.

Related Templates

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

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31