| Part | What it controls |
|---|---|
| Prompt | The extraction instructions for the AI agent |
| Schema | The field definitions and entity name |
| Data quality | The per-field validation rules |
| Notifications | Event subscriptions and notification channels |
| Frequency | How often linked workflows run |
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
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.Unlinking a workflow preserves its current configuration. The workflow keeps the prompt, schema, and notifications 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
- Schemas: Field definitions and data types used in template schemas
- Notifications: Event types and channels used in template notifications
- API Reference