← All N8N workflows
Automation & utilitiesCodeHTTP RequestIfManual TriggerWait

Motion-illustration Workflow Generated with Midjourney and Kling API

Configured with HTTP Request, Wait. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerWeb / APIKling Video GeneratorHTTP RequestWeb / APIGet VideoHTTP RequestCodeGet ImageCodeWeb / APIBasic PromptHTTP RequestRoutingGet Data StatusIfWaitWait for ImageGenerationWaitWeb / APIMidjourney ImageGeneratorHTTP RequestWaitWait for VideoGenerationWaitCodeGet Final Video URLCodeRoutingVerify Data StatusIf

Node categories in this workflow

  • Trigger
  • Web / API
  • Code
  • Routing
  • Wait

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Kling Video GeneratorWeb / APIHTTP RequestPOST
Get VideoWeb / APIHTTP RequestSee node parameters
Get ImageCodeCodeSee node parameters
Basic PromptWeb / APIHTTP RequestPOST
Get Data StatusRoutingIfSee node parameters
Wait for Image GenerationWaitWaitSee node parameters
Midjourney Image GeneratorWeb / APIHTTP RequestSee node parameters
Wait for Video GenerationWaitWaitSee node parameters
Get Final Video URLCodeCodeSee node parameters
Verify Data StatusRoutingIfSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

Motion-illustration

Motion-illustration

This workflow is primarily designed to generate dynamic illustrations for content creators and social media professionals with APIs provided by PiAPI.

Step-by-step Instruction

Step-by-step Instruction

  1. Fill in your x-api-key of your PiAPI account in the Midjourney Image Generator and Kling Video Generator nodes.
  2. Enter your desired image prompt in Basic Prompt node.
  3. Click Test workflow.
Motion-illustration Workflow Generated with Midjourney and Kling API

Motion-illustration Workflow Generated with Midjourney and Kling API

Purpose and structure

This folder contains the Motion-illustration Workflow Generated with Midjourney and Kling API workflow. Its executable nodes use code, httpRequest, if, manualTrigger, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/1484_Wait_Code_Create_Webhook.json MIT; preserve source notices.

More in Automation & utilities