Skip to main content
Workflow Studio configures the 15-phase Temporal pipeline that runs per brand. It is where you decide what the agent looks at, what it is allowed to do on its own, and when a human gets involved.

​
The pipeline

​
Templates

New brands start from a template that pre-fills 14+ phases, rather than configuring the pipeline from scratch: The workflow-narrow templates are useful when you want an agent that does exactly one job well, rather than a general assistant. What a template produces is an AutomationConfig — the same declarative contract the engine executes, so anything Studio can express is also editable as JSON and reviewable in a pull request:
Studio and the control plane can disagree about which version is live — Studio may show a draft the engine has not been given yet. Check the published version before concluding that an edit had no effect; a change that looks ignored is usually a change that was never published.

​
Context sources

The Context phase gathers from whichever sources you enable:

​
Gather strategy

context_gather_strategy controls what happens when a source is slow or unavailable:
best_effort keeps the pipeline moving when an integration is down, but the agent will answer from partial context — it may not know about a recent order. For flows that act on money or orders, prefer require_all or critical_only and let the gate escalate rather than answering on incomplete data.

​
Review gate

The Review phase is the safety boundary between what the agent generated and what the customer actually receives. Configured actions include: review_timeout_secs bounds how long a decision can pend, and escalation_always_review forces review on escalation paths regardless of other rules.

​
High-Value Actions

By default any action valued at $100 or more requires human approval before the engine executes it. This is configured per brand in the Review Gate phase.
This threshold is the main lever between autonomy and control. Lower it while you build trust in a new brand’s configuration, then raise it once the escalation and dispute rates look right.

​
Editing

The Studio editor supports:
  • List ↔ Graph view toggle (?view=graph for the visual editor)
  • ⌘K phase jumper
  • ⌘S save
  • Per-phase ? explainers
  • A pending-changes diff against the last saved config
Read the pending-changes diff before saving. Because a template pre-fills 14+ phases, it is easy to change more than you intended — the diff is the only place the full effect is visible.

​
Rollout

Workflow Studio is designed to be adopted in stages rather than switched on wholesale:
  1. Operator-led private beta — operators drive, the pipeline shadows.
  2. Assisted onboarding — configuration with support.
  3. Self-serve production — the customer configures their own brands.
An operator_shadow phase supports running the pipeline alongside a human without dispatching, so you can compare what the agent would have done against what the operator did.

​
Next steps

Configuration reference

Every AutomationConfig field, with the environment it runs in.

ResponseAutomationV2

The workflow a published config drives.

Control plane

Publishing and syncing configs across brands.

Website onboarding

Seeding a new brand’s rules from its own site.
Last modified on August 29, 2026