Skip to main content

Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack

Workflow preview

Workflow preview
100%
Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack preview
Open on n8n.io

1. Workflow Overview

Description This workflow is an AI powered lighting and look development pipeline designed for VFX production. It transforms a single lighting brief into multiple high quality cinematic lighting...

Best for

  • Content Creation automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.formtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.if, n8n-nodes-base.googledrive, n8n-nodes-base.slack, n8n-nodes-base.errortrigger

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Rahul Joshi.

Original n8n.io source

1.1 Workflow description

Title
Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack
Workflow name
Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack

📘 Description

This workflow is an AI-powered lighting and look development pipeline designed for VFX production. It transforms a single lighting brief into multiple high-quality cinematic lighting references using AI, automates rendering, organizes assets, builds a visual lookbook, and delivers structured outputs to the lighting team—bridging the gap between creative lighting direction and CG execution.

⚙️ Step-by-Step Flow

The workflow begins with a form-based trigger that acts as the lighting brief intake layer, allowing artists or supervisors to submit structured inputs such as shot code, sequence, project ID, plate image, lighting mood description, scene type, and CG subject type. This input flows into a validation and normalization stage, where required fields are verified, scene and subject types are mapped into standardized pipeline values, and the payload is structured for downstream processing. The system then performs prompt engineering and expands the single lighting brief into five distinct lighting variations: a key light setup for strong directional lighting, a soft diffuse setup for ambient lighting conditions, a high-contrast dramatic setup for stylized visuals, a plate-matched reference for accurate scene integration, and a final comp-grade preview simulating cinematic color grading. Each variation is enriched with detailed lighting instructions, scene context, and subject-specific attributes to guide realistic AI generation.

At the core of the pipeline, an image-to-video rendering layer constructs structured API requests and submits each variation as an independent job to the Seedance AI model, always using the plate image as a reference to maintain lighting consistency with the scene. A polling mechanism continuously monitors each job at regular intervals, ensuring that processing advances only after successful completion. Once rendering is complete, a metadata layer structures detailed information for each asset, including video URLs, lighting types, scene context, subject details, and generation timestamps, along with tagging for pipeline tracking and review status.

The asset pipeline then downloads the generated lighting reference videos and uploads them to Google Drive using a structured naming convention aligned with shot and variation identifiers. An aggregation layer consolidates all variations into a unified output and dynamically generates an HTML-based lookbook, presenting all lighting setups in a structured visual format with preview links, technical details, and usage guidance. This lookbook is stored in a Notion database for centralized tracking and documentation. Finally, an AI-driven messaging layer generates a clean, professional Slack notification summarizing the lighting brief, listing all generated variations with preview links, and prompting the lighting team to review and select the preferred direction before proceeding with CG lighting setup—ensuring seamless collaboration between creative intent and technical execution.

🚨 Error Handling

• Global error trigger across the workflow • Sends instant Slack alerts with failure details • Prevents silent failures and ensures production reliability

🧩 Prerequisites

• Seedance API (AI video generation) • n8n Form Trigger (input layer) • Google Drive OAuth2 (asset storage) • Notion API (lookbook tracking) • Slack OAuth2 (team notifications) • OpenAI API (AI-generated Slack messaging)

💡 Key Benefits

✔ Rapid lighting look development with multiple variations instantly ✔ Structured prompt engineering for consistent cinematic outputs ✔ Automated asset storage and organized lookbook generation ✔ AI-generated team communication for faster decision-making ✔ Seamless integration between creative direction and CG execution ✔ Scalable pipeline for production-ready lighting workflows

👥 Perfect For

  • Lighting artists and look development teams
  • VFX supervisors and creative directors
  • CG and rendering pipelines
  • Film and post-production studios
  • AI-assisted lighting and visualization workflows

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - n8n Form: Lighting Brief

Type / Role
n8n-nodes-base.formTrigger - formTrigger
Config choices
Version 2.2

Block 2 - Validate & Extract Lighting Brief

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Fan-Out: 5 Lighting Variations

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 4 - Build Lighting Request Body

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 5 - Seedance: Generate Lighting Ref

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 6 - Merge Lighting Job ID + Metadata

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Poll: Check Lighting Job Status

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 8 - Wait 20s

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 9 - Lighting Render Complete?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 10 - Build Lighting Asset Metadata

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Download Lighting Ref Video

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 12 - Google Drive: Upload Lighting Ref

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 13 - Aggregate + Build Lookbook

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 14 - Slack: Notify Lighting Team

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 15 - On Workflow Error

Type / Role
n8n-nodes-base.errorTrigger - errorTrigger
Config choices
Version 1

Block 16 - Slack: Error Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 17 - AI - Generate the slack message

Type / Role
@n8n/n8n-nodes-langchain.openAi - openAi
Config choices
Version 1.7

Block 18 - Record the log in Notion

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 19 - Sticky Note: Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Sticky Note: Form Intake

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note: Prompt Fan-Out

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note: AI Generation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note: Polling Loop

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note: Asset Storage

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack
Complexity advanced
Nodes 27
Categories Content Creation, Multimodal AI
Author Rahul Joshi
Published 08 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/14881/14881.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Generate Seedance AI lighting look dev variations with review via Drive, Notion, and Slack do?

Description This workflow is an AI powered lighting and look development pipeline designed for VFX production. It transforms a single lighting brief into multiple high quality cinematic lighting...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Multimodal AI use case.