Workflows

A workflow automates what happens when records change. Workflows are defined visually in Flow Designer, in the Admin area, and run server-side, so the same rules apply no matter where a change comes from — the UI, the REST API, or the Employee Center. For the state-based action buttons (CTAs) a workflow’s states expose on a record, see Tables, fields, choices and states.

Triggers

Workflows start from record events — create, update, a field reaching a value, an SLA timer, or a schedule.

Steps

Common steps include:

• Approval — route to an approver or group and wait for a decision. See Approvals for what an approver sees, and Design an approval workflow for how to build one.
• Notification — email or in-app message to the right people. See Email & notifications and Notifications.
• Create task — spawn child tasks (e.g. onboarding steps) with owners and due dates.
• Update field — set state, assignment or any value.
• Wait / timer — pause until a condition or SLA point.

SLAs and timers

Attach targets and timers to records by condition; workflows react to warnings and breaches — escalating, reassigning or notifying.