Which workflow type should you create, and what does that choice lock in?
You need a project first — see Create a project.
In Integration Manager:
For what those controls do on other types, see Flow controls.
- Select a project in the project list.
- Click Workflows.
- On the workflow list, click Create Workflow.
- In Create A New Workflow, fill in the fields below, then click Create Workflow.
Before you start #
- Create a project — required before you can create workflows in Integration Manager.
Create dialog fields #
| Field | What to enter |
|---|---|
| Workflow Name | A name you will recognize in the project list and editor. |
| Workflow Type | One of the four types in the table below — chosen at create time. |
| Project | The project this workflow belongs to. After you select a project and click Workflows, this field is usually already set. Change it only if you need a different project. |
Workflow name rules
- Minimum length: The name must be at least 5 characters. If it is too short, the form shows:
Workflow name must be at least 5 characters. - Unique in the project: The name must not match another workflow in the same project. Choose a different name if create fails for a duplicate.
At a glance #
| Type | Choose it when… |
|---|---|
| Asynchronous | Your main integration: steps run when the workflow is invoked (typical background / event-driven flow). Full canvas: modules, all flow controls, subflows. |
| Exception | Another workflow should run when a step fails (handler flow, not your main integration). |
| Audit | Another workflow should run for audit / trail logging tied to parent settings. |
Asynchronous #
Default type for building an integration on the canvas: modules, all flow controls, and subflows. Tasks follow your chain and branches when the workflow runs. After deploy, confirm behavior in run logs / deployments.Exception #
A supporting workflow referenced from a parent’s exception strategy when something goes wrong. It is not something you normally trigger like a main integration.Audit #
Same editor limits as exception. Runs when an audit strategy on a parent points at this workflow. Details under Workflow settings → Audit strategy.Workflow Editor limits (exception and audit) #
On exception and audit workflows:- Async Foreach and Scatter Gather are not in the Flow Control menu.
- Add Subflows shows:
Subflows are not supported for this workflow type.
For what those controls do on other types, see Flow controls.
English