Video Production Workflow in the Cloud

A sequence of steps that runs as one thing. Each step is an image render, an animation render, or a tool — and a step can use the output of an earlier step as its input.

Because the plumbing between steps is the tedious part: waiting for each job, carrying URLs forward, handling failures. A workflow does that and gives you one call and one result.

Render an image template, render an animation template, or run any tool.

By referencing it. Each step has a key, and a later step can point at that step’s output — the rendered video, the image URL — instead of a fixed value.

Define its inputs, then supply them when you run it. Steps reference those inputs the same way they reference each other’s outputs.

POST to the workflow’s run endpoint with its inputs. The run is queued and reports progress as each step completes.

No. The visual builder lists every step, the fields each one takes, and which earlier outputs you can reference. The fields come from the tools and templates themselves, so a new tool appears without anything else changing.

Yes. Each run records every step, its inputs, its outputs and how long it took, so a failure points at the step that caused it rather than the whole workflow.

The run stops there and the failure is recorded against that step, with the outputs of the steps that already succeeded still available.

The sum of its steps. There is no charge for the workflow itself.

A common one: render an animation from a template, burn subtitles onto it, add a logo overlay, then join it to an outro clip. Four steps, one call.

That is the point of inputs. Define the parts that change — a headline, an image URL, a name — and supply them per run.

Yes, you can publish it. Any image or animation templates it references are bundled with it, so installing the workflow gives the recipient the templates it needs as well.

The workflow and its bundled templates are copied into your workspace, and the steps are rewritten to point at your copies rather than the originals.

Three on a trial. They are counted per workspace.

A workflow decides what gets made. An integration decides what triggers it and where the result goes. They are often used together.

As long as its steps need — video work is not instant, and a workflow with several video steps takes minutes rather than seconds. Use the run’s progress or a webhook rather than holding a request open.