Publish blog posts from YouTube transcripts to WordPress and Telegram with Gemini
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Blog Post Generator Agent (v1.7) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (17)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Merge
n8n-nodes-base.merge - Aggregate
n8n-nodes-base.aggregate - Code
n8n-nodes-base.code - Google Docs
n8n-nodes-base.googleDocs - Telegram
n8n-nodes-base.telegram - Filter
n8n-nodes-base.filter - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Google Sheets Tool
n8n-nodes-base.googleSheetsTool - Google Docs Tool
n8n-nodes-base.googleDocsTool - Wordpress
n8n-nodes-base.wordpress - Edit Image
n8n-nodes-base.editImage
What it does
Who is this for? Content creators, media teams, and bloggers who run a YouTube channel and want to automatically repurpose video content into SEO-ready blog posts — without manual writing. Ideal for anyone publishing news or educational content in any language. What it does This workflow runs three fully automated pipelines that take a YouTube video all the way to a published WordPress post: Pipeline 1 — Transcript Collector runs on a schedule, fetches new videos from your YouTube playlist via the YouTube Data API, retrieves their full transcripts via RapidAPI, saves each transcript to a Google Doc, and logs metadata to Google Sheets. Pipeline 2 — AI Blog Generator picks up unprocessed transcripts, sends them to a Gemini AI Agent that reads the transcript and your existing published posts (for internal linking), then generates structured blog content: title, body (HTML), summary, tags, Telegram caption, image prompt, and publish priority. Results are saved to a second Google Sheet as pending. Pipeline 3 — Publisher runs every 3 hours, selects the highest-priority pending post (urgent > normal > evergreen), publishes it to WordPress, generates a featured image via an AI image API, uploads and attaches it to the post, then announces it to a Telegram channel. How to set up 1. Import this workflow into n8n. 2. Create two Google Sheets tabs: youtubeVideos and blogsAndNewsUploaded (column structures in the sticky notes). 3. Configure all credentials: Google (Sheets, Docs), YouTube API key, RapidAPI key (youtube-transcript3), Gemini API, WordPress, Telegram Bot, and your AI image generation API. 4. Set your YouTube Playlist ID in the first HTTP node. 5. Set your Google Drive Folder ID for transcript storage. 6. Activate all three schedule triggers independently. Requirements - YouTube Data API v3 key (Google Cloud Console) - RapidAPI subscription to youtube-transcript3 - Google Gemini API key - WordPress site with Application Password - Telegram Bot token + channel - AI image generation API (compatible with OpenAI images format) How to customize - Adjust the Gemini system prompt in the AI Agent node to change content language, tone, or structure. - Change publishpriority logic in the JS node to control posting frequency. - Swap the image generation API with any provider (DALL-E, Stability AI, etc.). - Add a Filter node before publishing to require manual approval of pending posts.