Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.


Log in to subscribe to topics and get notified when content changes.


Automate processes with a sequence of reusable actions such as manage records, ask for approvals, create tasks, and send notifications. Define trigger conditions to start a flow and variables to pass information between actions.

All flows consist of properties, a trigger, a sequence of actions, and the data collected or created.

Flow properties

The flow properties specify the flow name, application, description, and status. Flow designers can update the flow name and description at any time, but can only set the application during flow creation. The flow status is set when you save or activate a flow.


The trigger specifies the conditions that start the flow. When the trigger condition is true, the system starts the flow.

Flow Designer supports record-based and schedule-based trigger types.

Table 1. Record-based triggers
Trigger Description
Created Starts a flow when a record is created in a specific table.
Updated Starts a flow when a record is updated in a specific table. Requires selecting whether to always run the trigger or to only run it once.
Created or Updated Starts a flow when a record is either created or updated in a specific table. Requires selecting whether to always run the trigger or to only run it once.
Note: Flows including approval actions should only run the trigger once.
Table 2. Schedule-based triggers
Trigger Description
Daily Starts a flow at a specific time every day.
Weekly Starts a flow at a specific time every week.
Monthly Starts a flow at a specific time every month.
Run Once Starts a flow once at a specific time but does not repeat.
Repeat Starts a flow at regular intervals you define.


Each action is a set of reusable business logic that produces a specific outcome when provided with its input values. Flow designers configure actions by specifying where they go in a flow sequence and by selecting the data they use as input values. As a flow runs, actions earlier in the sequence generate outcomes or output values that become available as data to actions later in the flow.

By default, the system provides a collection of core actions that can be added to any flow. Core actions cannot be viewed or edited from the Action Designer interface. Some applications include spokes which add application-specific flows and actions. Spoke actions are typically read-only but can be copied and customized. Developers may also create their custom actions from the Action Designer interface.

Flow data

Flows store any data gathered or generated as variables in the Data pane. Each variable has its own pill that Flow designers can use to drag-and-drop the variable value to an action input or output. Flow Designer generates the pill name based on the contents and its data type. The system specifies the variable data type next to the pill.

Figure 1. Example flow data

Flow logic

Flows may contain flow logic to specify conditional or repeated actions. The system provides these flow logic options.

Table 3. Available flow logic
Flow logic Description
For each Applies actions to each record in a list of records. Flow designers must specify the list of records from the flow data.
If Applies actions when a list of conditions is met. Flow designers can use flow data to specify the conditions.

Testing flows

After adding a trigger and one or more actions, flow designers can test a flow. Testing a flow sets the trigger conditions to true and runs all actions. For flows that have record-based triggers, flow designers may specify an existing test record to use as input. Flow designers should always test flows on non-production instances containing relevant demonstration data since testing a flow creates or changes records on the instance.

Flow execution details

The system generates flow execution records, log messages, and reports for each flow run. The flow context is a related record containing the current state and runtime values of the flow. The system generates a context record each time a flow is run.


To access Flows, a user must have the flow_designer or admin roles.