Skip to main content
Templates let you define a reusable configuration (setup prompt, schema, data quality rules, notifications, run frequency, and record limit) and apply it to multiple workflows. When you update the template, you can push changes to all linked workflows at once. A template can include any combination of these parts: Each part is optional. For example, a template can define only a schema, or a schema and notifications without a prompt. For guidance on what to put in each part and how to roll out changes safely, see Template Best Practices.

​
Versioning

Templates are versioned. Every time you save changes, a new version is published. Versions are immutable. Once published, a version cannot be edited. This means you can:
  • Roll out updates to linked workflows selectively
  • Roll back to a previous version if needed
  • See exactly what changed between versions
  • Preview the data impact of a new version on a linked workflow before applying it

​
Linking Workflows

When you link a workflow to a template, the template’s configuration is applied to the workflow. The configuration managed by the template becomes read-only on the workflow, and you can manage it through the template UI instead. To modify a template-managed field on a workflow, either update the template and apply the change, or unlink the workflow first. The setup prompt works differently from the other parts. It is read once, when a workflow is created from the template. Publishing a new prompt changes what new workflows start with; workflows that have already been built keep the instructions they started with.
Unlinking a workflow preserves its current configuration. The workflow keeps the prompt, schema, rules, notifications, and frequency it had. They become editable again from the workflow itself.

​
Managing Templates

In the UI

Create and manage templates visually in the dashboard.

Via API

Create and manage templates programmatically with the REST API or MCP Server.

​
Learn More