HumationHuman + Automation
Back to Catalog

Generate video from an image with ByteDance Seedance 1.5 Pro via KIE.AI

Muhammad Farooq IqbalMuhammad Farooq Iqbal
357 views
2/3/2026
Cloud StorageGoogle DriveOpenAIAutomationPDF
Official Page

This n8n template demonstrates how to generate animated videos from static images using ByteDance Seedance 1.5 Pro model through the KIE.AI API. The workflow creates dynamic video content based on text prompts and input images, supporting custom aspect ratios, resolutions, and durations for versatile video creation.

Use cases are many: Create animated videos from product photos, generate social media content from images, produce video ads from static graphics, create animated story videos, transform photos into dynamic content, generate video presentations, create animated thumbnails, or produce video content for marketing campaigns!

Good to know

  • The workflow uses ByteDance Seedance 1.5 Pro model via KIE.AI API for high-quality image-to-video generation
  • Creates animated videos from static images based on text prompts
  • Supports multiple aspect ratios (9:16 vertical, 16:9 horizontal, 1:1 square)
  • Configurable resolution options (720p, 1080p, etc.)
  • Customizable video duration (in seconds)
  • KIE.AI pricing: Check current rates at https://kie.ai/ for video generation costs
  • Processing time: Varies based on video length and KIE.AI queue, typically 1-5 minutes
  • Image requirements: File must be publicly accessible via URL (HTTPS recommended)
  • Supported image formats: PNG, JPG, JPEG
  • Output format: Video file URL (MP4) ready for download or streaming
  • Automatic polling system handles processing status checks and retries

How it works

  1. Video Parameters Setup: The workflow receives video prompt and image URL (set in 'Set Video Parameters' node or via trigger)
  2. Video Generation Submission: Parameters are submitted to KIE.AI API using ByteDance Seedance 1.5 Pro model
  3. Processing Wait: Workflow waits 5 seconds, then polls the generation status
  4. Status Check: Checks if video generation is complete, queuing, generating, or failed
  5. Polling Loop: If still processing, workflow waits and checks again until completion
  6. Video URL Extraction: Once complete, extracts the generated video file URL from the API response
  7. Video Download: Downloads the generated video file for local use or further processing

The workflow automatically handles different processing states (queuing, generating, success, fail) and retries polling until video generation is complete. The Seedance model creates smooth, animated videos from static images based on the provided text prompt, bringing images to life with natural motion.

How to use

  1. Setup Credentials: Configure KIE.AI API key as HTTP Bearer Auth credential
  2. Set Video Parameters: Update 'Set Video Parameters' node with:
    • prompt: Text description of the desired video animation/scene
    • image_url: Publicly accessible URL of the input image
  3. Configure Video Settings: Adjust in 'Submit Video Generation Request' node:
    • aspect_ratio: 9:16 (vertical), 16:9 (horizontal), 1:1 (square)
    • resolution: 720p, 1080p, etc.
    • duration: Video length in seconds (e.g., 8, 10, 15)
  4. Deploy Workflow: Import the template and activate the workflow
  5. Trigger Generation: Use manual trigger to test, or replace with webhook/other trigger
  6. Receive Video: Get generated video file in the output, ready for download or streaming

Pro tip: For best results, ensure your image is hosted on a public URL (HTTPS) and matches the desired aspect ratio. Use clear, high-quality images for better video generation. Write detailed, descriptive prompts to guide the animation - the more specific your prompt, the better the video output. The workflow automatically handles polling and status checks, so you don't need to worry about timing.

Requirements

  • KIE.AI API account for accessing ByteDance Seedance 1.5 Pro video generation
  • Image File URL that is publicly accessible (HTTPS recommended)
  • Text Prompt describing the desired video animation/scene
  • n8n instance (cloud or self-hosted)
  • Supported image formats: PNG, JPG, JPEG

Customizing this workflow

Trigger Options: Replace the manual trigger with webhook trigger for API-based video generation, schedule trigger for batch processing, or form trigger for user image uploads.

Video Settings: Modify aspect ratio, resolution, and duration in 'Submit Video Generation Request' node to match your content needs (TikTok vertical, YouTube horizontal, Instagram square, etc.).

Prompt Engineering: Enhance prompts in 'Set Video Parameters' node with detailed descriptions, camera movements, animation styles, and scene details for better video quality.

Output Formatting: Modify the 'Extract Video URL' code node to format output differently (add metadata, include processing time, add file size, etc.).

Error Handling: Add notification nodes (Email, Slack, Telegram) to alert when video generation fails or completes.

Post-Processing: Add nodes after video generation to save to cloud storage, upload to YouTube/Vimeo, send to video editing tools, or integrate with content management systems.

Batch Processing: Add loops to process multiple images from a list or spreadsheet automatically, generating videos for each image.

Storage Integration: Connect output to Google Drive, Dropbox, S3, or other storage services for organized video file management.

Social Media Integration: Automatically post generated videos to TikTok, Instagram Reels, YouTube Shorts, or other platforms.

Video Enhancement: Chain with other video processing workflows - add captions, music, transitions, or combine multiple generated videos.

Aspect Ratio Variations: Generate multiple versions of the same video in different aspect ratios (9:16, 16:9, 1:1) for different platforms.

n8n Workflow: Generate Video from an Image with ByteDance Seedance 1.5 Pro via Kie AI

This n8n workflow demonstrates a foundational structure for interacting with an external API to generate content, potentially a video from an image, using a manual trigger. While the specific API calls are not fully defined in the provided JSON, the workflow sets up a robust pattern for making HTTP requests, processing responses, and handling different outcomes.

What it does

This workflow outlines the following steps:

  1. Manual Trigger: The workflow is initiated manually by clicking the 'Execute workflow' button.
  2. Edit Fields (Set): Placeholder for setting up or transforming data before making an API call. This node is typically used to prepare input data, such as image URLs or other parameters required by the video generation API.
  3. HTTP Request: This is the core action where an API call would be made to an external service (e.g., Kie AI, which might integrate with ByteDance Seedance 1.5 Pro). This node is configured to send a request and receive a response.
  4. Switch: After the HTTP request, this node acts as a conditional router. It likely checks the status or content of the API response to determine the next steps. For example, it could check if the video generation was successful or if further processing is needed.
  5. Wait: If a specific condition is met (e.g., the video generation is still in progress, or a callback is expected), this node introduces a delay, allowing time for the external service to complete its task.
  6. Code: This node provides the flexibility to execute custom JavaScript code. It could be used for advanced data manipulation, error handling, or parsing complex API responses.
  7. Sticky Note: A descriptive note within the workflow, likely used for documentation or to provide context about a specific section.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n to import and execute the workflow.
  • API Endpoint and Credentials: An API endpoint for the video generation service (e.g., Kie AI, ByteDance Seedance 1.5 Pro) and any necessary authentication credentials (API keys, tokens, etc.) will need to be configured within the "HTTP Request" node.
  • Input Data: Depending on the API, you will need to provide the necessary input data, such as an image URL, which would be prepared in the "Edit Fields" node.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Open the "HTTP Request" node.
    • Set the URL, Method (e.g., POST), and Headers (including Authorization if required with your API key/token) according to the documentation of the video generation API.
    • Configure the Body of the request to send the necessary data (e.g., image URL, video parameters).
  3. Prepare Input Data:
    • Open the "Edit Fields" node.
    • Define the fields that will hold your input data, such as the image URL, which will then be used in the "HTTP Request" node.
  4. Configure Switch Logic:
    • Open the "Switch" node.
    • Define the conditions based on the expected API response (e.g., checking for a status field, a video_url presence, or an error message).
  5. Adjust Wait Time:
    • If the "Wait" node is used, adjust its duration based on the typical processing time of the video generation service.
  6. Customize Code Node:
    • If specific post-processing or error handling is needed, modify the JavaScript code within the "Code" node.
  7. Execute the workflow: Click the "Execute workflow" button on the "Manual Trigger" node to run the workflow.

This workflow provides a flexible template for integrating with external APIs for content generation, allowing for customization of input, request parameters, and response handling.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942