Understanding the Four Step Types

Every workflow in Aitomic Flow is built from four node types on the canvas. Knowing what each type does is the foundation for designing effective workflows.

Trigger

The Trigger node is the fixed starting point of every workflow. It has no configuration and no assignee — it marks where a flow begins when someone clicks Start Flow.

• Every workflow has exactly one Trigger node; it cannot be deleted
• The person who clicks Start Flow becomes the requester — this identity is referenced by assignee rules such as "Requester" and "Manager of Requester"
• The Trigger node sits on the left edge of the canvas and cannot be moved independently of the canvas layout

Action

The Action node is where real work happens. When the workflow reaches an Action step, the system assigns it to a person and waits for them to fill in the form and click Submit.

Each Action step can be configured with:

• Form fields — collect data from the assignee (text, numbers, dates, files, selections)
• Assignee rule — determines who receives the step at runtime
• SLA deadline — optional; the step is flagged overdue if not completed within N hours of assignment
• Escalation — optional; the assignee's manager is notified automatically if the step is not actioned within N hours

Most workflows consist largely of Action nodes. A typical approval flow is: Submit (Action) → Approve/Reject (Action) → Process (Action).

Branch

The Branch node routes the workflow along a Yes path or a No path based on conditions you define. Conditions evaluate field values from any upstream Action step.

• Both the Yes and No output handles must be connected before you can publish
• Branch nodes have no form fields and no assignee — they execute instantly when reached
• Multiple conditions can be added; all must be true for the flow to take the Yes path (AND logic)

Use Branch nodes any time the workflow should behave differently based on an outcome — for example, routing an approved request to one team and a rejected one back to the requester.

Complete

The Complete node is the fixed end point of a workflow path. When an instance reaches Complete, it is marked as completed and no further steps are processed.

• A workflow can have multiple Complete nodes — typically one at the end of each branch path
• Complete nodes have no configuration
• Cycle time (used in Flow Performance reports) is measured from the Trigger to the first Complete node reached

Typical workflow patterns

Linear (no branching):
Trigger → Action → Action → Complete

Single approval with two outcomes:
Trigger → Action (Submit) → Action (Decision) → Branch → Action (Approved path) → Complete
→ Action (Rejected path) → Complete

Multi-stage approval:
Trigger → Action → Action → Branch → Action → Complete
→ Complete

See also

• How to Create a Workflow
• How Branch Conditions Work
• All Assignee Rule Types Explained