Step Names and Descriptions: Best Practices

Every Action and Branch step has a label (shown on the canvas and in emails) and an optional description (admin-only). Naming steps clearly helps admins maintain flows and helps assignees understand their tasks.

The label

The label appears:

• On the canvas node
• In Flow Performance and SLA reports (as the step name)
• In the assignee's task notification email and task form

Because assignees see the label, write it for a human reader — not as an internal code.

Label guidelines

Use verb–noun format: "Approve request", "Submit expense", "Review contract"

Be specific: Avoid "Step 1", "Approval", "Review". Instead: "Manager approval", "Legal review", "Finance sign-off"

Keep it concise: 2–5 words. Longer labels are truncated on the canvas.

Examples

❌ Poor	✅ Better
Step 2	Manager approval
Approval	Finance sign-off
Process	HR processing
Review	Legal contract review

The description

Optional free text visible only in the step configuration panel. Assignees never see it.

Use it to:

• Explain why the step exists or what outcome is expected
• Document which role should be assigned
• Note edge cases: "Only fires if amount > 5000 via the branch above"
• Leave notes for the next admin who edits the flow

Naming Branch and Complete nodes

Branch: Rename from the default "Branch" to reflect the decision: "Manager decision", "Amount threshold", "Priority check"

Complete: In flows with multiple Complete nodes, give each a name: "Approved and processed", "Rejected — returned to requester"

See also

• Understanding the Four Step Types
• How to Create a Workflow