Templates

Reusable, versioned configurations that standardize prompt, schema, and notifications across workflows

Templates let you define a reusable configuration — prompt, schema, and notifications — 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 three parts:

Part	What it controls
Prompt	The extraction instructions for the AI agent
Schema	The field definitions and entity name
Notifications	Event subscriptions and notification channels

Each part is optional. For example, a template can define only a schema, or a schema and notifications without a prompt.

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 parts managed by the template become read-only on the workflow — you manage them through the template 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 just become editable again.

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