Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

Action Nodes

Action nodes are the building blocks of Actionflows, they are represented as a circle with an icon. They perform specific tasks, e.g. updating data, performing calculations, and API integrations, and are joined together using connectors.

Action nodes can be dragged from the toolbar onto the canvas to create a new action, and some can be clicked to see existing objects, e.g. click

Insert excerpt
_action_screen
_action_screen
nopaneltrue
 to list existing screens, then drag from the Repository onto the canvas.

Most nodes run once per record they receive from the input connection point. However, some nodes only trigger once after receiving the final record or once per flow, e.g. 

Insert excerpt
_action_screen
_action_screen
nopaneltrue
,
Insert excerpt
_action_phase
_action_phase
namestart
nopaneltrue
 and
Insert excerpt
_action_url
_action_url
nopaneltrue
 nodes.


Excerpt
namemapping

Attributes are mapped into action nodes as Input Parameters and out of action nodes as Output Attributes. Connectors between the action nodes then pass through the data and attributes. Every attribute is passed through* but in order to use an attribute in a specific action node it must be mapped in to it as an input parameter.

*although there can be exceptions, such as the Converge action.

Tip

Once mappings are configured they will reused in all instances of the Actionflow. This is because the action nodes sit within the Actionflow itself and only the data coming into and out of an Actionflow changes for each instance.


Note: The specifics of mappings and connectors are covered in a later in this course.