Building and publishing a workflow
The canvas
The name at the top is editable, with a status pill beside it — draft, active or paused — and a N to fix chip when something would stop it publishing.
The right-hand panel is one tool at a time, chosen from the rail: Assistant, Add a step, Step settings, Before you publish, Works in (which project it belongs to), Memory, Runs, and Suggested improvements.
The assistant
You can build by describing what you want. The assistant edits the canvas alongside you rather than replacing it — you can always take over.
Testing
- Test run proves the wiring against a payload you supply. Nothing real
happens.
- Try one for real (after publishing) runs the live version once.
The difference matters: a test proves the shape, a real run proves the effect.
Publishing
Publish refuses while blockers exist, and the checklist lets you jump straight to the step at fault. Blockers are deliberate — a schedule faster than every five minutes, a step that declares an output nobody reads, a send to a channel we can't actually deliver on.
After publishing, the ⋯ menu offers Pause schedules, Try one for real, Share with org, Share to library, Export as .owf, Duplicate and Tidy up the layout.
Watching runs
The Runs tool and the Runs segment show every execution, what it received, and where it got to.
When a workflow needs you
A step can be set to stop and ask before it sends, posts or spends. Those land in Approvals — see Approving what a workflow wants to do.