Connect workspace actions

Canvas becomes a workflow when one node supplies a required input to another. Connections make the dependency visible: they show what the next action will use and help preserve the reasoning behind an output.

Choose nodes by responsibility

Keep each node focused. Use image, video, audio, text, Assembly, or Lip Sync nodes for the action they represent. A workflow is easier to review when a source asset, transformation, and final result are not hidden inside one oversized step.

Connect compatible inputs

Connect a source node to the matching input on the destination. Specialized actions make their requirements explicit:

• Assembly accepts ordered video clips;
• Lip Sync accepts one source video and dialogue audio;
• generation routes accept only the reference media types supported by the selected model.

An edge is not only a visual line. It identifies the asset the downstream action should use. If the destination remains incomplete, inspect whether the connected source has a ready, usable asset.

Understand dependency runs

A downstream action may wait for connected upstream work to finish. A queued state can therefore mean the workflow is waiting for an earlier node rather than failing. Avoid starting duplicate work until the dependency state is clear.

Keep the graph readable

Arrange inputs before outputs, name important nodes by purpose, and avoid crossing unrelated campaign branches. Review the connections before an expensive run; the right prompt with the wrong source connection still produces the wrong workflow.

Use Assemble video clips and Create a lip-sync video for the two specialized media actions.