Action Nodes and Elements

Action nodes are THEN statements, and they define how to process the content specified by the trigger and any additional conditions. An action node must always be the last node at the end of any path within your flow.

Unlike other node types, an action node can contain only one action element.

Older versions of Flow Automations allowed you to have more than one action element within an action node. To prevent flows from malfunctioning, nodes created before this change might still contain more than one element. New action nodes, however, will allow only one action element. Consider recreating the flow so each action element is within its own node.

You can connect action nodes to trigger, condition, and even other action nodes with a base edge or a branch edge. You can also connect an action node and condition node together with an else branch edge.

When you connect an action node to another action node or condition node as a child, if the parent action node is successful, processing continues from the parent node to the child node.

A flow can have more that one action node, and by default, a flow can have a maximum of 100 actions.

If 100 action elements are insufficient, contact professional services to discuss your options to increase this limit.

For more information, see:

• Community Flow Actions

• Care Flow Conditions