Skip to main content
A workflow is one trigger and a list of steps that run in order when the trigger happens. Tasks track work for people and agents, documents hold rich text with comments, and notifications tell people what happened.

​
Workflows

​
Trigger kinds

A workflow has exactly one trigger. The kind is one of these values.

​
Step kinds

A step’s kind is action or branch.
  • action runs an action: update a record, create one, send a notification, or call an action a module declares.
  • branch chooses which steps run next, based on a condition.

​
Runs

Every execution of a workflow is a run. A run has a status of pending, running, succeeded or failed, and records the outcome of each step. A run is saved step by step, so a restart does not lose it. A step whose action reports a temporary failure, such as a service being busy, is tried again later by itself. See Workflow runs and retries.

​
Limits

​
Who a workflow acts as

A workflow acts as itself, not as a person. It can read and write records and run module actions, and it cannot change the workspace’s settings. A module can ship workflows of its own. A workspace can switch those on or off, or copy them.

​
Tasks

A task is a unit of work for a person or an agent. It has a status and a priority, and it can be linked to records and documents. Tasks are shown as a list or a board.

​
Documents and comments

Documents are rich-text pages with comments and @mentions. Records and tasks have comments too.

​
Notifications

Workflows, modules and agents can notify people. Notifications appear behind the bell in the studio. A notification can address people by role: owner, admin or member.