Varosity
All guides

Save as workflow template

Save a project as a reusable workflow; start new projects from it or from a curated template (UI, CLI, MCP).

Save as workflow template

Built a project structure you'll want to reuse? Save it as a workflow template. The graph (shots, models, durations, music attachment, voice attachment) gets snapshotted; outputs are NOT included.

From the studio

Open a project → top-right overflow menu → Save as workflow.

  • Name — the human-friendly title (e.g. "Founder podcast promo")
  • Description — what this workflow is for
  • Public — opt-in to share it in the Community section of
  • /app/workflows

Instantiating

Your saved workflows (UI)

/app/workflows → pick one from Yours or Community → Use this workflow. You land in a fresh project with the same shot structure, ready to edit and render.

Saved workflows run from the UI only today — there is no CLI command or MCP tool that runs a workflow you saved.

Curated templates (MCP; CLI coming in 0.1.1)

The MCP server (and, from CLI 0.1.1, the CLI) exposes Varosity's curated storyboard templates (product demo, testimonial, social hook, explainer). Cloning one creates a project with its shots laid out; you then render and stitch as usual.

The varosity templates commands are coming in CLI 0.1.1 (the published 0.1.0 doesn't have them); the MCP tools work today.

# CLI 0.1.1+
varosity templates list
varosity templates use <slug> --name "Founder podcast promo"
# → Cloned · <projectId>

From MCP:

{ "name": "list_templates", "arguments": {} }
{ "name": "create_project_from_template", "arguments": {
  "slug": "<slug from list_templates>",
  "name": "Founder podcast promo"
}}

create_project_from_template returns { projectId, shotCount }. Over REST the same clone is POST https://varosity.ai/api/v1/projects/from-template/{slug} with an optional { "name": "…" } body.

Why this matters for agents

A template turns the planning half of a multi-shot flow into one call: the agent clones the structure, then renders each shot and calls render_project for the final stitch — no studio session required.