# Manage workflow templates

A workflow template combines a reusable definition with a parameter schema. It is separate from an instantiated workflow, an app template, and an immutable reusable recipe.

Use the Assistant's supported template-management operations to inspect or propose changes when no dedicated management control is available. Review the proposed definition and parameters before approving a write.

## Define a template

A template has a name, optional description, tags, a workflow definition, and `parameters_schema`. Choose a clear name and describe its input, output, and external effects. Tags help people discover related recipes.

Use `${parameter_name}` placeholders where the instance should supply a value, such as its workflow name or source identity. A placeholder occupying an entire value preserves the supplied JSON type, so an integer limit remains an integer. A placeholder inside longer text interpolates into that text.

The parameter schema declares fields, types, required values, and defaults. An omitted optional field can take its declared default; an explicit supplied value takes precedence. Runtime variables used by a handler, such as an idempotency template's run identity, are distinct from instantiation parameters and should not be replaced with a fixed value accidentally.

## Create and check

1. Inspect a working example of the intended workflow.
2. Identify which settings should vary between instances.
3. Define matching placeholders and parameter fields.
4. Ask the Assistant to propose creating the reusable template.
5. Review its name, definition, schema, defaults, and tags before approving.
6. Instantiate a new test workflow and validate its rendered jobs.
7. Run a small example and inspect the actual destination.

Saving a template does not replace validation of its rendered workflow. A placeholder can be legal text in a template while becoming an invalid connection, JSONPath, or handler setting when supplied incorrectly.

## Update or retire

Read the current template before proposing an edit. Name, description, tags, parameter schema, and definition can change; changing the definition advances its template version. Existing workflows remain their own instances and are not silently rewritten.

Template updates do not provide the same version-precondition or automatic Undo protection as some other Assistant changes. Coordinate edits and review the latest contents before approving replacement values.

Deleting a workflow template through the Assistant requires administrator permission and explicit approval. It permanently removes the starter; workflows already created from it remain. Use a replacement starter and communicate changed parameters before removing one people still rely on.

See [template directory](/docs/workflow-templates/overview), [workflow versions](/docs/workflows/versions), and [reusable recipes](/docs/workflows/reusable-recipes).