Transform YouTube videos to social media content with Vizard AI and GPT-4.1
Transform YouTube Videos to Social Media Content with Vizard AI and GPT‑4.1
Overview
This n8n template fetches new YouTube videos, enriches them with Vizard AI metadata, generates social‑media captions using GPT‑4.1, logs everything to Google Sheets, and notifies you by email. It’s a turnkey solution for content creators and marketers who need an end‑to‑end automated pipeline from video publishing to post scheduling.
Setup Instructions
-
Import the Template
- In n8n, click Import from JSON, paste this workflow, and save.
-
Configure Credentials
- Vizard AI: Create an HTTP Request credential named
Vizard APIand set yourVIZARDAI_API_KEY. - OpenAI: Add a new OpenAI credential for GPT‑4.1.
- Google Sheets: Create a Google Sheets OAuth2 credential with read/write access or just sign in if your on cloud hosting
- Gmail: Add a Gmail OAuth2 credential for email notifications or just sign in if you are on cloud hosting
- Vizard AI: Create an HTTP Request credential named
-
Adjust Limits
- In the Limit Videos node, set
maxItemsto control batch size.
- In the Limit Videos node, set
Google Sheets Column Structure
| Column | Description |
| ------------------ | ---------------------------------------------------- |
| videoId | Unique YouTube video identifier |
| projectId | Vizard AI project ID returned |
| videoUrl | Original YouTube video URL |
| title | Video title |
| transcript | Transcribed text from Vizard AI |
| viralScore | Vizard AI’s viral‑score metric |
| viralReason | Explanation for viral score |
| generatedCaption | GPT‑4.1–generated caption in JSON { "caption": ""} |
| clipEditorUrl | URL to Vizard’s clip editor |
Workflow Steps
- Read YouTube RSS Feed (
Read YouTube RSS Feed) - Limit Videos (
Limit Videos to N) - Send to Vizard (
Create Vizard Project&Retrieve Vizard Metadata) - Split Items for Processing (
Iterate Each Video) - Generate Captions (
Generate Social Media Captions) - Append Row in Sheet (
Log to Google Sheets) - Send Notification (
Email Summary)
Customization Tips
- Alternate Caption Styles: Modify the AI prompt for tone, length, or brand voice.
- Localization: Extend prompts for other languages.
- Notification Channels: Swap Gmail for Slack, Teams, or SMS via webhook nodes.
n8n Workflow: YouTube to Social Media Content with Vizard.ai and GPT-4
This n8n workflow automates the process of transforming YouTube videos into social media content using Vizard.ai for video processing and OpenAI's GPT-4 for text generation. It's designed to streamline content creation for marketers, creators, and businesses looking to repurpose long-form video into engaging short-form content.
What it does
This workflow performs the following key steps:
- Triggers Manually: The workflow is initiated manually, allowing you to control when the content generation process begins.
- Fetches YouTube Video URLs: It reads a list of YouTube video URLs from a specified Google Sheet.
- Limits Processing: It processes a limited number of videos at a time to manage API usage and workflow execution.
- Loops Through Videos: For each YouTube video URL:
- It sends the YouTube video URL to Vizard.ai for processing.
- It waits for a short period to allow Vizard.ai to begin processing.
- It retrieves the processed video data from Vizard.ai.
- It extracts relevant text content from the Vizard.ai response.
- It uses OpenAI (likely GPT-4, given the directory name context) to generate social media content (e.g., captions, tweets, short summaries) based on the extracted text.
- It sends an email notification with the generated content or a summary.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Sheets Account: Configured credentials for Google Sheets to read YouTube video URLs.
- Vizard.ai Account: An API key or credentials for Vizard.ai to process videos.
- OpenAI Account: An API key for OpenAI (e.g., GPT-4) to generate text content.
- Gmail Account: Configured credentials for Gmail to send email notifications.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file for this workflow.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- Locate the "Google Sheets" node and configure your Google Sheets credentials. Specify the spreadsheet name and sheet name where your YouTube video URLs are listed.
- Locate the "HTTP Request" nodes that interact with Vizard.ai and configure the necessary API keys or authentication headers.
- Locate the "OpenAI" node and configure your OpenAI API key.
- Locate the "Gmail" node and configure your Gmail credentials.
- Customize Workflow (Optional):
- Google Sheets: Adjust the "Google Sheets" node to point to your specific spreadsheet and sheet containing YouTube video URLs. Ensure the column containing URLs is correctly referenced.
- Limit: Modify the "Limit" node if you want to process more or fewer videos in a single execution.
- Vizard.ai Integration: Review the "HTTP Request" nodes for Vizard.ai to ensure they match the current Vizard.ai API documentation for submitting videos and checking status.
- OpenAI Prompt: Customize the prompt in the "OpenAI" node to refine the type and style of social media content generated (e.g., "Generate 3 Twitter threads," "Write a LinkedIn post summarizing the video").
- Gmail Notification: Adjust the "Gmail" node to send notifications to your preferred email address and customize the email subject and body with the generated social media content.
- Wait Time: Adjust the "Wait" node duration if Vizard.ai processing typically takes longer or shorter.
- Execute the Workflow:
- Click the "Execute Workflow" button on the "When clicking ‘Execute workflow’" node to run the workflow manually.
- Monitor the execution in n8n to ensure it runs successfully.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte