Build · Workflow
Design, test, publish and run a workflow
From a plain-language description to a governed, metered run with approvals and ROI posting.
Step by step
Each step is a governed Action: it is permission-checked, logged, and either reversible or compensated.
- 1
Describe the process in plain language or pick a template
- 2
AI drafts steps, mappings and assumptions
- 3
Builder edits the draft on the canvas
- 4
Validation checks entitlements, schemas, permissions and loop risk
- 5
Test run or dry run with a sample record or payload
- 6
Drafts with R3 or R4 steps go to a second approver who sees the diff
- 7
Version is published and a trigger fires
- 8
Each step re-checks entitlement, permission, policy and budget, pausing with a reason if denied
- 9
Approval steps wait in the Approvals Inbox or on WhatsApp
- 10
Actions execute via the Action Bus; audit, events and cost lines are written; the run posts to the ROI Ledger
More Build workflows
See how One3 would run your business
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.