Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Motion Illustration Automation

Motion Illustration Automation is a 11-node automation blueprint connecting Midjourney API, Kling API. Inspect its trigger, execution graph, branches, and implementation requirements.

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

11

Nodes

12

Links

1

Run groups

Connected tools

2 integrations

  • Midjourney API
  • Kling API

Canvas controls

Fit wide systems, then zoom into any run group.

Motion Illustration Automation execution lanes1 run groups containing 11 workflow nodes and 12 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTBasic Prompt. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Basic PromptINTEGRATIONHTTPREQUEST1 IN / 1 OUTMidjourney Image Generator. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 03Midjourney Image GeneratorINTEGRATIONHTTPREQUEST2 IN / 1 OUTWait for Image Generation. integration node, wait. 1 incoming and 1 outgoing connections.STEP 04Wait for Image GenerationINTEGRATIONWAIT1 IN / 1 OUTGet Data Status. decision node, if. 1 incoming and 2 outgoing connections.STEP 05Get Data StatusDECISIONIF1 IN / 2 OUTGet Image. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Get ImageTRANSFORMCODE1 IN / 1 OUTKling Video Generator. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Kling Video GeneratorINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet Video. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 08Get VideoINTEGRATIONHTTPREQUEST2 IN / 1 OUTVerify Data Status. decision node, if. 1 incoming and 2 outgoing connections.STEP 09Verify Data StatusDECISIONIF1 IN / 2 OUTWait for Video Generation. integration node, wait. 1 incoming and 1 outgoing connections.STEP 10Wait for Video GenerationINTEGRATIONWAIT1 IN / 1 OUTGet Final Video URL. transform node, code. 1 incoming and 0 outgoing connections.OUTCOMEGet Final Video URLTRANSFORMCODE1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.11 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

When clicking ‘Test workflow’

12 Execution Links
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Basic Prompt

    Integration

  3. Step 3

    Midjourney Image Generator

    Integration

  4. Step 4

    Wait for Image Generation

    Integration

  5. Step 5

    Get Data Status

    Decision

  6. Step 6

    Get Image

    Transform

  7. Step 7

    Kling Video Generator

    Integration

  8. Step 8

    Get Video

    Integration

  9. Step 9

    Verify Data Status

    Decision

  10. Step 10

    Wait for Video Generation

    Integration

  11. Outcome

    Get Final Video URL

    Transform

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.