Convert YouTube Videos into SEO Blog Posts
Configured with Gmail, HTTP Request, Markdown, Open Ai. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
- AI & models
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Get YouTube Transcript | Web / API | HTTP Request | POST |
| Set Variables | Transform | Edit Fields | See node parameters |
| Generate Blog Post | AI & models | Open Ai | See node parameters |
| Generate AI Image | Web / API | HTTP Request | POST |
| Gmail | Messaging | Gmail | See node parameters |
| Markdown | Transform | Markdown | See node parameters |
| Download Image | Web / API | HTTP Request | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2httpBearerAuthhttpHeaderAuthopenAiApi
Workflow notes
Set Variables
Set Variables
Set your variables here, such as:
- YouTube Video URL: The YouTube video you want to convert into a SEO Blog Post
- Recipient Email Address: This is the email we send all generated content to at the end of the workflow.
Get YouTube Transcript
Get YouTube Transcript
This step gets the transcript of the YouTube video with Dumpling AI. The target video must have captions or subtitles enabled. You can modify this to specify a language.
Generate Blog Post
Generate Blog Post
Here we get GPT-4o (or a model of your choice) to generate a detailed SEO blog post. We ask for:
- title
- description
- blogImagePrompt
- content
To improve this step, you can consider generating section by section or replacing this with an AI Agent with research capabilities
Generate Blog Image
Generate Blog Image
Here we use the FLUX.1-dev model via Dumpling AI to generate a image for the blog post. Feel free to use the image model you prefer. You may need to update to a more powerful (expensive) model if you want text in your images.
Convert Markdown to HTML
Convert Markdown to HTML
OpenAI LLMs tend to output markdown. We need to convert to HTML for formatting in the the Gmail node.
Download Image for Attachment
Download Image for Attachment
The image URL is a temporary URL, so we need to download the image and attach it to the email being sent.
Send blog post via email for next steps
Send blog post via email for next steps
We send all generated content to your email address so you have a record of all generations and can get it ready for publication
Convert YouTube Videos into SEO Blog Posts
Convert YouTube Videos into SEO Blog Posts
Purpose and structure
This folder contains the Convert YouTube Videos into SEO Blog Posts workflow. Its executable nodes use gmail, httpRequest, manualTrigger, markdown, openAi, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Manual/1241_Manual_HTTP_Process_Webhook.json MIT; preserve source notices.