Generate AI videos from text prompts with OpenAI Sora 2
Sora 2 Video Generation: Prompt-to-Video Automation with OpenAI API
Who’s it for
This template is ideal for content creators, marketers, developers, or anyone needing automated AI video creation from text prompts. Perfect for bulk generation, marketing assets, or rapid prototyping using OpenAI's Sora 2 API.
Example use cases:
-
E-commerce sellers creating product showcase videos for multiple items without hiring videographers or renting studios
-
Social media managers generating daily content like travel vlogs, lifestyle videos, or brand stories from simple text descriptions
-
Marketing teams producing promotional videos for campaigns, events, or product launches in minutes instead of days
How it works / What it does
- Submit a text prompt using a form or input node.
- Workflow sends your prompt to the Sora 2 API endpoint to start video generation.
- It polls the API to check if the video is still processing or completed.
- When ready, it retrieves the finished video's download link and automatically saves the file.
- All actions—prompt submission, status checks, and video retrieval—run without manual oversight.
How to set up
-
Use your existing OpenAI API key or create a new one at https://platform.openai.com/api-keys
-
Replace Your_API_Key in the following nodes with your OpenAI API key: Sora 2Video, Get Video, Download Video
-
Adjust the Wait node for Video node intervals if needed — video generation typically takes several minutes
-
Enter your video prompt into the Text Prompt trigger form to start the workflow
Requirements
- OpenAI account & OpenAI API key
- n8n instance (cloud or self-hosted)
- A form, webhook, or manual trigger for prompt submission
How to customize the workflow
- Connect the prompt input to external forms, bots, or databases.
- Add post-processing steps like uploading videos to cloud storage or social platforms.
- Adjust polling intervals for efficient status checking.
Limitations and Usage Tips
-
Prompt Clarity: For optimal video generation results, ensure that prompts are clear, concise, and well-structured. Avoid ambiguity and overly complex language to improve AI interpretation.
-
Processing Duration: Video creation may take several minutes depending on prompt complexity and system load. Users should anticipate this delay and design workflows accordingly.
-
Polling Interval Configuration: Adjust polling intervals thoughtfully to balance prompt responsiveness with API rate limits, optimizing both performance and resource usage.
-
API Dependency: This workflow relies on the availability and quota limits of OpenAI’s Sora 2 API. Users should monitor their API usage to avoid interruptions and service constraints.
Generate AI Videos from Text Prompts with OpenAI Sora (Placeholder)
This n8n workflow is designed to facilitate the creation of AI-generated videos from text prompts. While the current workflow structure appears to be a placeholder or an initial draft, it lays the groundwork for a system that could integrate with advanced AI video generation services like OpenAI Sora (once publicly available).
Important Note: Based on the provided JSON, this workflow currently contains only a trigger and foundational logic nodes. It does not yet include any actual integration with an AI video generation service. The title and description reflect the intended purpose, which would require further development.
What it does (Intended Functionality)
The current workflow structure suggests the following intended steps:
- Receives Text Prompts: It is designed to start when a user submits a text prompt via an n8n form.
- Makes an HTTP Request: It includes an HTTP Request node, which would typically be used to send the text prompt to an external API for processing (e.g., an AI video generation service).
- Conditional Logic: An "If" node is present, indicating that the workflow might branch based on certain conditions after the HTTP request (e.g., checking the response status, content, or specific parameters).
- Introduces a Delay: A "Wait" node suggests that there might be a need to pause the workflow, perhaps to await the completion of a long-running video generation task.
- Provides Notes: Sticky notes are included, likely for documentation or to mark areas for future development and integration.
Prerequisites/Requirements
To fully realize the intended functionality of this workflow, you would need:
- n8n Instance: A running instance of n8n.
- OpenAI Sora API Key (or similar AI Video API): Once available, an API key for OpenAI Sora or another AI video generation service (e.g., RunwayML, Synthesia, etc.) that can convert text prompts into video.
- API Endpoint: The specific API endpoint for the chosen AI video generation service.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure the n8n Form Trigger:
- Open the "On form submission" node.
- Define the fields for your form, ensuring one field is designated for the text prompt that will be sent to the AI.
- Activate the workflow to get the webhook URL for your form.
- Configure the HTTP Request Node (Future Step):
- Edit the "HTTP Request" node.
- Set the "Method" to
POST(or as required by the AI service). - Enter the API endpoint URL for your chosen AI video generation service.
- Add the necessary "Headers" (e.g.,
Authorizationwith your API key,Content-Type: application/json). - In the "Body" section, construct the JSON payload to send your text prompt (from the "On form submission" node) to the AI service.
- Configure the If Node (Future Step):
- Define the conditions within the "If" node based on the expected response from the AI video generation API. This might involve checking for success status, error messages, or the presence of a video URL.
- Configure the Wait Node (Optional/Future Step):
- Adjust the "Wait" duration if you need to pause the workflow for a specific period (e.g., to allow the AI service time to process the video).
- Extend the Workflow (Future Development):
- Add nodes to handle the AI service's response (e.g., download the generated video, post a link to Slack/Discord, save to cloud storage, update a database).
- Implement error handling for failed video generation requests.
- Activate the Workflow: Once configured, activate the workflow to start processing form submissions and generating videos.
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