Automated blog creation from news to publication using Gemini, Ideogram & Slack
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 12 nodes and runs on a schedule (legacy Cron node). Along the way it connects Slack and Google Gemini. It also calls newsapi.org and api.replicate.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- Fetch Industry Trends (HTTP Request): calls newsapi.org
- Message a model (Google Gemini): uses Google Gemini
- Message a model (Google Gemini): uses Google Gemini
- Code: runs custom JavaScript code
- HTTP Request: calls api.replicate.com (POST)
- HTTP Request: calls an HTTP API
- Wait: waits 20 seconds
- If: checks a condition and branches into true / false
- Edit Fields (Edit Fields (Set)): sets or maps fields
- Publish to Supabase (HTTP Request): calls an HTTP API (POST)
…plus 1 more step. See the full node list below.
Services it uses
HTTP calls to: newsapi.org, api.replicate.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron in Schedule Trigger: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Schedule Trigger | Schedule Trigger |
Nodes used (8)
- HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Code
n8n-nodes-base.code - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Cron
n8n-nodes-base.cron
From the author
The AI Blog Creator with Gemini, Replicate Image, Supabase Publishing & Slack is a fully automated content generation and publishing workflow designed for modern marketing and SaaS teams. It automatically fetches the latest industry trends, generates…