Creating and running a Blueprint
Draft and Published versions, Templates, and Simulation — what each does and how to use it, in plain language.
This page covers creating and managing a Blueprint, day to day. For a full explanation of every node type and the Workflow Debugger, see the Workflow Guide.
What is a Blueprint?
A Blueprint is a reusable, versioned definition of a multi-step AI-driven workflow — the steps, their order, who does each one, and what happens if something fails. You design a Blueprint once, then run it as many Missions as you need.
Every Blueprint lives in a specific workspace and is built visually in the Builder — click a step type from the catalog on the left to add it to the canvas.
Draft, Published, Deprecated
Draft ──Publish──► Published (v1, v2, v3 …) ──► Deprecated ──► Retired ▲ │ └──── keep editing ──────┘ (Published versions never change)
Draft is your current, always-editable working copy — every Blueprint has exactly one. Clicking Save saves the Draft; Publish turns it into a new, numbered, permanent version. A Published version is never edited again — to change behavior, edit the Draft and publish a new version. Only a Published version can be used to start a real Mission.
Creating a Blueprint
- Open Blueprints in the sidebar.
- Click New blueprint and give it a name.
- In the Builder, click a step type in the left-hand catalog to add it to the canvas — start with Agent Task for any piece of work an AI agent should carry out.
- Select a step to edit its name and, for a Sub Workflow step, which Blueprint it calls, in the Inspector panel on the right.
- Click Save, then Publish when you're ready to run it as a real Mission.
Templates
A Template is a Blueprint that has been shared or certified for reuse. Browse them under Workflow Studio → Template Library — cloning a template never modifies the original, you always get a fresh, independent Draft to edit.
Simulation — "What would happen if I ran this?"
Click Simulate in the Builder's header to see how a Blueprint would run — without starting a real Mission, without calling a real AI provider, and without any cost.
What you get on the results page:
- A Timeline of every step, in order — click any step to inspect it.
- For an Agent Task step: the resolved prompt (clearly labeled "mock — never sent to a real provider") and a placeholder mock output.
- Predicted cost and predicted latency — both explicitly labeled mock/illustrative, not a real bill and not based on historical data.
- A Sub Workflow step's own steps are simulated too, nested underneath it.
Simulation works on a Draft too — you don't need to publish a Blueprint first to try it out.
Current limits, stated plainly: only Agent Task and Sub Workflow steps have real simulated behavior today. Decision, Condition, Loop, and similar step types are shown in the Timeline (their type and position are real) but don't yet have configurable logic to simulate — the same limitation the Builder itself has for those step types. Editing a value and re-running instantly from the results page isn't available yet either.
Frequently Asked Questions
Does Simulate cost anything or use my provider's quota? No — it never calls a real AI provider. Every prompt and output shown is mock data.
Can I simulate an unpublished Draft? Yes — Simulation works on either a Draft or a Published version.
Why does my prompt still show {topic} instead of a real value? Simulation substitutes sample values you provide; if none were given for a field, it shows the placeholder as-is rather than guessing.