Create and Deploy a Workflow
A workflow is a BPMN diagram — drawn in any BPMN 2.0 editor (e.g. Camunda Modeler, free and open source) — that the console turns into a running, governed process.
1. Add the workflow
Go to BPMN Workflows → Add BPMN Workflow:
- Organization / Project.
- Workflow Key — e.g.
feature-delivery. - Execution Code — a short code (2-10 uppercase letters/numbers) used in run ids.
- Name / Category / Description.
- BPMN XML or JSON Definition — paste the exported BPMN from your diagram tool. A live preview of the diagram appears as you paste.
- Initial Config JSON — leave the default
{}; you'll assign agent profiles visually in the next step instead of hand-writing this.
Click Create.
Assigning Agent Profiles to tasks
Click any service task box in the diagram — the Service Task panel opens on the right:
- Agent Profile — pick which profile runs this step. Every service task needs one before the workflow can run; the console flags any that are missing.
- Worker Selection — use Auto for normal provider/capacity matching, Pinned for one worker key, or Capability to require advertised features. Dispatch still requires an approved online worker with a compatible provider adapter and a free slot.
Repeat for every service task in the diagram. Human approval steps (drawn as a plain user task, e.g. "Approve Feature Delivery") don't need an agent profile — they pause for a person instead.
2. Publish and deploy
Once every task has an assignment, click Publish v1. This locks the version, deploys it to the workflow engine, and makes the workflow ready to run. Editing after that creates a new draft version — publish it the same way (Publish v2, etc.) when you're ready; the previous version keeps running any instances already using it.
Finally, make sure the workflow itself is enabled (not suspended) — only an enabled workflow with a published version can be run.
Reusing one diagram across multiple tech stacks
A common pattern: keep one generic diagram (e.g. "Feature Delivery"), then create a second Workflow entry per stack from the same exported BPMN, just changing the Workflow Key/Name and re-pointing each implement/test/commit task's Agent Profile to the stack-specific one (profile-go-dev, profile-java-dev, profile-react-dev, ...). Each becomes its own independently versioned, independently deployed workflow.