Create personal workflow templates

A personal workflow template preserves a useful Canvas structure so you can apply it to future work. It is private to your account and uses the same application pipeline as maintained templates.

Prepare the source workspace

Build and test the workflow before saving it. Select only the nodes that belong to the reusable process and the connections between them. Functional text, image, video, and Assembly nodes can be captured by the current builder; unsupported node types are rejected instead of silently disappearing.

Save the Canvas before reviewing the template. If the Canvas changes while the template is being captured, save can reject the outdated revision so the template does not preserve an unintended structure.

Define reusable inputs and output

Map the source nodes that should be replaced in each use to clear input names. Choose the output that represents completion. Keep prompts and generation settings that genuinely belong to the process, but remove campaign-specific language that would make the template misleading elsewhere.

Execution identifiers are not reused. Generated assets can become previews, while original source assets remain reusable inputs. Saving a template does not run generation and does not charge credits automatically.

Apply and inspect

When you apply the template, the resulting nodes belong to the destination workspace and remain editable. Replace the inputs, confirm the active brand, review models and estimates, and inspect the graph before running it.

Archive safely

Removing a personal template prevents normal future reuse but does not remove nodes already created in existing workspaces. Treat the template definition and each applied workflow as related but separate objects.

Start with Use workflow templates for the application flow.