A saved workflow is not a template

A saved workflow is a reusable video recipe: scenes, assets, style, and model stored so you can run it again with a fresh plot. A one-tap template is a photo-in finished clip with no scene graph. The last MP4 is not the reusable object. The recipe is. Saving a template export in a folder does not become a workflow. Cloning a public recipe does. This page is that object, from the recipe door.

The template-is-not-a-workflow page starts on the shelf. Start here when someone says "we templated it" and means they liked an export.

What actually gets stored

The graph: scene order, prompts, the asset map, house style, the video model. A first run can follow the saved scenes exactly. A re-run writes a new plot around the same cast so the next episode is not a repost. Saving a draft does not generate a clip.

What belongs in the saved object:

Scene list you can edit.
Reusable character and product keys, not adjectives hoped from chat history.
Caption family and kit mapping, if the show has a face in type.
A model pick per shot you are willing to change later without rebuilding five scenes from memory.

What does not get stored, and should not be confused with this object:

A brand kit. Kit is default colours and tone applied to whatever you make. The workflow consumes it. It is not the recipe.
Batch generation. Several jobs in one sitting. Not a graph you come back to.
A style-preset. A look on one generation.
The MP4 from last Tuesday. That is an export. Scheduling it is a repost.

Recreating a public card from the workflows library clones this object into your account. That is how you start from someone else's recipe without authoring one. You then swap the asset map. That swap is the recast. A template does not have an asset map. You would be swapping a still on a joke format, which is a different door.

The glossary pitfall is generating the same five scenes from chat every week because nothing was saved. Whoever is on the desk rewrites wardrobe. Identity drifts. The caption family wanders. You do not have a show. You have a habit of prompting.

A template has no graph to reopen

One-taps lock motion before you arrive. Finger-snap and mugshot already decided the cut. Required input is a hosted still. There is no scene two to retake. There is no product key to point at. There is no place to say "use Seedance on the pack hold and Veo on the talk."

If you needed those sentences, you were never on the template shelf. You were in a workflow and you opened the wrong card because it was faster. Faster is allowed for a joke. It is expensive for a SKU series.

Consequences of treating the export as the recipe:

You cannot change the product shot without re-running the whole joke on a new still, and the joke may not be a pack hold.
You cannot fail over a row. Veo 3.1 at 64 credits versus Kling O3 Pro text to video at 56 credits is a shot decision inside a recipe. A template will not take it.
You cannot put a recurring series clock on a new plot. You can cron the same template. That is a still factory, not episodes.
You cannot register a cast. Named assets belong to a workflow id or a slideshow schedule id. They do not belong to a trend card.

Agent-named jobs split this on purpose: run a one-tap template is photo in, clip out. Save and run a workflow is the graph. Mixing the verbs in Slack is how a producer asks for "the template" and means the five-scene matcha recipe.

Re-run means a new plot, not "try again"

Open the editor to change a product or a scene. Do not open it to reroll the same plot because you did not like the seed. Rerolling is a generate. The saved object is the show bible plus machinery.

Lock wardrobe, palette, and pacing across scenes before the first save. That pass is what makes a re-run still look like one show. If you save chaos, you will schedule chaos. Content velocity will look healthy. The format will not be.

A series clock sits on this object, or on a slideshow premise, not on a template. Plain-English cadence is enough for the agent to write the schedule. The schedule is not a render. A run is, and it can auto-post with a written caption if you asked. Pause when the format dies. A clock on a dead recipe is faster failure, same as a clock on a dead template, except the recipe was supposed to be the thing you trusted.

Captions: burn after the plate is locked, one family. The AI caption generator is not a template and not a workflow. It is a finish. Put the family name in the recipe so the finish does not reinvent the show.

Rights do not live in the workflow JSON. A twin used as a cast member still needs a replica grant. A SKU still needs to be the real SKU. Article 50 (2 August 2026) still wants a label on photoreal synthetics for EU audiences. Saving the recipe does not disclose. Saving the recipe does not licence.

Save the graph, leave the shelf for jokes

If the job is a known trend and a still, use the one-tap. Do not clone a workflow to imitate a finger-snap. You will pay for scenes the joke does not have.

If the job is a show, save a workflow. Clone a public recipe when the shape exists — Morning Matcha Routine is a character-held face across scenes, which is continuity, not a licence to scrape a creator. Author from scratch when the shape does not exist.

The AI video generator remains the single-shot launcher. It does not store a five-scene graph. Do not build a series by remembering last week's prompt.

If the week is "store the recipe, not the MP4," sign up and stop calling exports templates and templates series.

FAQ

Is a saved draft the same as a saved workflow?

A draft that holds the graph is the workflow. A draft that is only a prompt in chat is not. If you cannot recast the asset map, you do not have the object yet. Save until you can.

Can I schedule a one-tap as if it were a workflow?

You can run it on a habit. You cannot give it a new plot engine or a cast key. If you need episodes, author the joke as scenes and save that. Do not pretend the shelf grew a graph.

Does cloning a public workflow copy someone else's licence?

It copies a recipe shape. It does not copy a talent grant, a music licence, or a SKU you do not own. Swap the asset map to your consented files before you publish.