Templates
Workflow templates are pre-built workflow configurations that you can install into any project. They provide ready-to-use workflows with pre-configured stages, agent roles, tool assignments, and routing -- so you can start running workflows immediately without building everything from scratch.
What a Template Contains
A template packages a complete workflow blueprint:
| Component | Description |
|---|---|
| Name | Display name of the template |
| Description | What the workflow does and when to use it |
| Category | Grouping label (e.g., "content", "research", "development") |
| Difficulty | Complexity rating: beginner, intermediate, or advanced |
| Blueprint | The full workflow configuration as a JSON object -- stages, assignments, outcomes, routing, hooks, and all settings |
| Metadata | Summary data including agent IDs, stage count, and feature tags |
| Sample Events | A recorded sequence of workflow run events showing what the template produces |
Browsing the Template Library
The template library is accessible from the workflow creation flow. Templates are displayed as cards showing:
- Template name and description
- Category badge
- Difficulty rating
- Stage count and agent IDs (from metadata)
- Feature tags highlighting what the template demonstrates (e.g., "branching", "tool use", "multi-agent review")
Templates can be filtered by category using the category selector. They are sorted by position (curated order) and then by name.
Template Metadata
The metadata field provides quick-glance information without needing to parse the full blueprint:
| Key | Type | Description |
|---|---|---|
agent_ids | Array of strings | The agent IDs used in the blueprint (e.g., ["Researcher", "Anna", "Editor"]) |
stage_count | Integer | Number of stages in the workflow |
features | Array of strings | Feature tags describing what the template demonstrates |
This metadata powers the template cards in the library browser, giving users a quick sense of the template's scope and complexity.
Installing a Template
When you install a template into a project, the platform:
- Creates a new team with agents matching the template's agent roles.
- Creates a new workflow with stages, assignments, outcomes, routing, and hooks matching the blueprint.
- Links the workflow to the newly created team.
The installed workflow is a fully independent copy. After installation, you can modify any part of it -- rename stages, change agent perspectives, adjust routing, add or remove tools -- without affecting the original template.
Installing a template creates new resources in your project. It does not create a live link to the template. Future updates to the template do not propagate to installed instances.
What You Need Before Installing
Templates assume certain platform resources are available:
- LLM Configuration -- You will need to assign an LLM to the created team. Templates do not bundle API keys or LLM configurations since those are organization-specific.
- Skills and Tools -- If the template references specific tools, those tools must exist in your project's tool library or be available through installed skills.
- Credentials -- If tools require API keys, you must configure the appropriate credentials in your organization's settings.
After installation, review the created team and workflow to fill in any organization-specific configuration.
Sample Runs
Templates can include sample events -- a pre-recorded sequence of workflow run events that demonstrate what the template produces when executed. Sample events let you preview a template's behavior before installing it.
Each sample event contains:
| Field | Description |
|---|---|
sequence | The order of the event in the run |
event_type | The type of event (e.g., stage start, agent message, tool call, stage complete) |
data | The event payload showing what happened |
Sample events are displayed in the template detail view, rendered as a simulated workflow run timeline. This gives you a concrete picture of the agents' interactions, tool usage, and outputs.
Template Difficulty
The difficulty rating helps you choose templates appropriate to your experience level:
| Level | Description |
|---|---|
| Beginner | Simple workflows with 1-2 stages and straightforward linear execution. Good for learning the platform. |
| Intermediate | Multi-stage workflows with branching, loops, or multi-agent collaboration. Demonstrates more advanced features. |
| Advanced | Complex workflows with sophisticated routing, subagent spawning, hooks, and tool orchestration. |
Field Reference
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Name | String | Yes | -- | Unique template name |
| Slug | String | Yes | Auto-generated | URL-friendly identifier (generated from name) |
| Description | Text | No | -- | What the template does |
| Category | String | No | -- | Grouping label |
| Difficulty | Enum | Yes | -- | beginner, intermediate, or advanced |
| Blueprint | JSON | Yes | {} | Full workflow configuration |
| Metadata | JSON | No | {} | Summary data (agent IDs, stage count, features) |
| Sample Events | JSON Array | No | [] | Pre-recorded run events for preview |
| Position | Integer | No | 0 | Display order in the library |