Getting started
Use this path to stand up a first automation in the console.
Open Studio
- Sign in to console.exemplar.dev and select an organization.
- From the sidebar Build group, open Automation Studio (
/automation-studio).
You land on Mission Control: searchable workflows (filter by Draft / Active / Paused / Archived), a live-runs strip, and pending approvals.
First workflow
Create
Click New workflow. Studio opens the Build lens with an empty canvas (?workflow=new).
Add a trigger
Open Add step and pick a trigger:
- API trigger — invoke manually from Trace (Run now) or via REST
- Event trigger — start on a platform event
- Schedule trigger — run on a cron schedule
Add steps
From the catalog, add Logic, Actions, Connectors, AI agents, or Human approval. Steps auto-connect from the selected node. Configure each step in the inspector (right panel).
Validate, save, publish
Use the Build toolbar:
- Validate — catch graph / payload issues early
- Save — persist a version (first save assigns a workflow id and updates the URL)
- Publish — make the version runnable
Trace only sees the published graph. Unsaved Build edits are not auto-published.
Run and inspect
Switch to the Trace lens (?lens=trace). For an Active workflow with an API trigger:
- Click Run now (pick a trigger if there are several)
- Watch the canvas overlay and timeline update as steps execute
- Open a step for input / output and condition detail
If the graph includes Human approval, pending tasks appear under Approve and on Mission Control’s approvals strip.
Honest flow: Build → Publish → Trace → Run now. Publishing is required before live runs; Studio empty-states deep-link you back to Build when a workflow is not yet active.
Deep links
| URL | View |
|---|---|
/automation-studio | Mission Control |
?workflow=<id> or ?workflow=new | Workspace (Build by default) |
?workflow=<id>&lens=trace | Trace |
?workflow=<id>&lens=trace&run=<runId> | Trace focused on a run |
?workflow=<id>&lens=approve&task=<taskId> | Approve focused on a task |