Automate SEO blog creation from trends using Gemini AI, Apify, and Google Docs
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 13 nodes and runs on a schedule (every day at 08:00). Along the way it connects Google Gemini Chat Model. It also calls api.apify.com and api.kie.ai over HTTP.
How it runs
Trigger: On a schedule (every day at 08:00).
- Fetch Google Trends (HTTP Request): calls api.apify.com (POST)
- Generate SEO Blog Content (AI Agent): runs an AI agent, with model: Refine Content with Gemini AI; output parser: Parse Blog Output
- Format output for Google Docs (Code): runs custom JavaScript code
- Generate Blog Image (HTTP Request): calls api.kie.ai (POST)
- Update Google Doc (HTTP Request): calls an HTTP API (POST)
- Check Image Generation Status (HTTP Request): calls api.kie.ai
- Is Image Ready? (If): checks a condition and branches into true / false
- Wait: pauses before continuing
- Prepare Image URL for Insert (Edit Fields (Set)): sets or maps fields
- Download Image (HTTP Request): calls an HTTP API
Services it uses
HTTP calls to: api.apify.com, api.kie.ai
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Wait
n8n-nodes-base.wait
From the author
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…