HumationHuman + Automation
Back to Catalog

Generate text-to-video & image-to-video content with Seedance 1 Lite AI

Yaron BeenYaron Been
1523 views
2/3/2026
OpenAIAutomationAI SummarySalesforceCRM
Official Page

Generate Text-to-Video & Image-to-Video Content with Seedance 1 Lite AI

Built with n8n + Replicate

This workflow takes a prompt (and optional seed), sends it to Bytedance’s seedance-1-lite model, waits for processing, and returns a generated video.

⚡ Section 1: Start & Authenticate

  • ▶️ On clicking ‘execute’ → Manual trigger to start the workflow.
  • 🔑 Set API Key → Stores your Replicate API key so all requests are authorized.

Benefit: Keeps your API credentials secure and reusable.

🛠️ Section 2: Send Video Generation Request

  • 📡 Create Prediction → Makes a POST request to Replicate with:

    • prompt: your text description of the video
    • seed: (optional) controls randomness for reproducibility
    • Model version: b6519549e375404f45af5ef2e4b01f651d4014f3b57d3270b430e0523bad9835

Benefit: Kickstarts AI video generation from just a simple text prompt.

🔍 Section 3: Track the Prediction

  • 📦 Extract Prediction ID → Stores predictionId, status, and predictionUrl for polling.

  • ⏳ Wait → Pauses 2 seconds between checks.

  • 🔁 Check Prediction Status → Calls Replicate to see if the video is ready.

  • ✅ Check If Complete → Branches:

    • If status = succeeded → continue.
    • Else → loop back to Wait until it’s finished.

Benefit: Ensures the workflow patiently monitors progress without timing out.

📽️ Section 4: Process & Return Results

  • 📦 Process Result → Outputs a clean response containing:

    • status
    • video_url (generated video)
    • metrics
    • created_at & completed_at
    • model: bytedance/seedance-1-lite

Benefit: Gives you structured data and the direct video link, ready to share or store.

📊 Workflow Overview

| Section | Purpose | Key Nodes | Benefit | | ------------------- | --------------------------- | --------------------------------------------- | ------------------------------- | | ⚡ Start & Auth | Initialize & secure API key | Manual Trigger, Set API Key | Keeps credentials safe | | 🛠️ Send Request | Start video generation | Create Prediction | Submits prompt to Replicate | | 🔍 Track Prediction | Poll status until done | Extract Prediction ID, Wait, Check Status, If | Reliable async handling | | 📽️ Process Result | Format output | Process Result | Easy access to final video link |

✅ Final Benefits

  • 🎬 Generate AI-powered videos directly from text prompts.
  • 🔑 API key stored securely within workflow.
  • 🔄 Handles asynchronous processing with automatic polling.
  • 📤 Provides clean, ready-to-use JSON output including video URL.
  • 🧩 Flexible — you can connect results to Slack, Google Drive, or YouTube for instant publishing.

n8n Workflow: Seedance 1 Lite AI Content Generation

This n8n workflow provides a basic framework for interacting with an AI service, potentially for generating text-to-video or image-to-video content, and includes conditional logic and data manipulation capabilities.

What it does

This workflow outlines a process that can be customized for various AI content generation tasks:

  1. Manual Trigger: The workflow is initiated manually, allowing for on-demand execution.
  2. Edit Fields (Set): Placeholder for setting or modifying data fields before making an API request. This could be used to prepare prompts, configuration parameters, or other input data for the AI service.
  3. HTTP Request: Makes an API call to an external service. This node is typically configured to send data to an AI model (like Seedance 1 Lite AI, based on the directory name) and receive a response.
  4. If: Introduces conditional logic. This node can be configured to evaluate the API response or other data and route the workflow based on specific conditions (e.g., success/failure, type of content generated).
  5. Wait: Pauses the workflow for a specified duration. This can be useful for waiting for asynchronous AI processing to complete or to introduce delays between steps.
  6. Code: Allows for custom JavaScript execution. This node can be used for advanced data processing, transformation, or integration logic that is not covered by standard n8n nodes.
  7. Sticky Note: Provides a place for comments or documentation within the workflow itself, enhancing readability and understanding.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • AI Service API (e.g., Seedance 1 Lite AI): Access to an AI service capable of generating video or image content from text or other inputs. This will likely require an API key or authentication credentials.
  • API Endpoint: The specific URL for the AI service's API.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" to create a new workflow.
    • Go to "File" > "Import from JSON" and paste the copied JSON.
  2. Configure Nodes:
    • Edit Fields (Set) (Node 38): Configure this node to set the necessary input data for your AI service. This might include text prompts, image URLs, style preferences, or other parameters.
    • HTTP Request (Node 19):
      • Set the URL to your AI service's API endpoint.
      • Configure the Method (e.g., POST).
      • Add any required Headers (e.g., Authorization with your API key).
      • Set the Body to send the data prepared in the "Edit Fields" node.
    • If (Node 20): Customize the conditions based on the expected response from your AI service. For example, check for a status code, a specific field in the response indicating success, or the type of content generated.
    • Wait (Node 514): Adjust the Time parameter if you need to introduce a delay.
    • Code (Node 834): If advanced logic is required, write your custom JavaScript code here to process the AI service's response or prepare data for subsequent steps.
  3. Activate the Workflow: Once configured, activate the workflow.
  4. Execute Manually: Click the "Execute Workflow" button on the "When clicking ‘Execute workflow’" (Manual Trigger) node to run the workflow.

This workflow provides a flexible foundation for automating interactions with AI content generation services. You can expand upon it by adding nodes for storing generated content (e.g., Google Drive, S3), notifying users (e.g., Slack, Email), or further processing the output.

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