Templates¶
Status: Current | Last reviewed: 2026-06-24
Templates let you save reusable building blocks so you don't rebuild the same thing every time. They live under Tools & Templates in the left nav, split across Agent Templates (agent, stage, and subagent blueprints), Workflow Templates (workflow blueprints), and Prompt Templates (reusable prompt text — see Prompt templates).
Open Agent Templates and use the segmented control at the top to switch between agent, stage, and subagent template kinds. Open Workflow Templates for workflow blueprints.
Agent templates¶
A full agent blueprint. These are what the New Agent Wizard offers when you pick a type and a technology stack (for example OpenAI Speech Agent or Google ADK Speech Agent) — each is an agent template behind the scenes.
- New — choose a name and a category (Voice Agent, Chat Agent, Copilot, Translation). This creates a blank blueprint and opens it in the standard agent editor, where you build it exactly like a normal agent.
- Edit — opens the blueprint in the agent editor.
- Delete — removes the blueprint. Agents already created from it are not affected.
Add a template here whenever you want a new option to appear in the wizard — a new provider, a new starting configuration, a new agent style.
Templates you create belong to your tenant — you can edit and delete them. The built-in templates that ship with the product (the ones the wizard offers out of the box) are shared across tenants and shown read-only; only platform administrators can change those.
Stage templates¶
A single reusable pipeline node — a prewritten stage with its provider, model, prompt, and other settings already filled in. Use these so authors can drop a ready-made stage into a pipeline instead of configuring one from scratch.
- New / Edit — opens a modal with the same node-editing experience as the pipeline editor's inspector. Give the template a name, description, and tags, then configure the stage (provider, service, model, prompt, and so on). A stage template may include subagents.
- Delete — removes the template.
Workflow templates¶
A full reusable workflow blueprint. Use these when teams should start from a known pattern instead of a blank graph.
- New — choose a name, workflow type, tags, and description. This creates a blank blueprint and opens it in the standard workflow editor.
- Edit — opens the blueprint in the workflow editor. You use the same graph, node inspector, settings sheet, undo/redo controls, and validation experience as a normal workflow, but runtime-only controls such as publish, run history, and testing are hidden.
- Delete — removes the template. Workflows already created from it are not affected.
Workflow templates appear in the New Workflow picker. Choosing one copies its config into a new workflow; editing the new workflow does not change the template.
Subagent templates¶
A single reusable specialist subagent. Same idea as a stage template, but scoped to a subagent.
- New / Edit — opens a modal where you set a name, description, tags, and the subagent's own prompt and tools.
- A subagent template cannot contain nested subagents — that option is hidden here. (A stage template can.)
Using a template in the editor¶
Templates show up where you add things on the canvas:
- Click New workflow on the Workflows page. Search the Template list to start from a workflow template, or choose Scratch for a blank workflow.
- Click a “+” on the pipeline canvas. Alongside the from-scratch stage options, a From a template section lists your stage templates. Pick one and a new stage is added, pre-filled from the template.
- When adding a sub-agent inside an orchestrator stage, the picker lists subagent templates and Start from scratch only. Pick a template to drop in a ready-made specialist, or start blank and configure its prompt and tools in the subagent editor.
Seeding from a template copies its settings into a brand-new node — editing the new node never changes the template, and changing the template later never alters nodes already created from it. When the copied stage, agent, subagent, or workflow has an empty integration profile field, TrueServe binds the tenant's default active profile for that provider. If there is no default but exactly one active profile is available, that single profile is used; multiple active profiles with no default stay blank.