Action Nodes

• 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,
• Once a mapping is configured you it 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) 

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 wired together.

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  Open Screen to list existing screens, then drag from the Repository onto the canvas.

Most nodes run once per record they receive on their driving connection point. However, some nodes only trigger once after receiving the final record or once per flow, e.g.  Open Screen,  Start Phase and  Open URL nodes.

Usually, action nodes have  Driving connections, which pass data through to the next action node. Some action nodes have a   Lookup connection, which send out a request for data, that is then returned to the action node data. 

Nodes must be connected sequentially starting from the  Driving interface connection point. Records will then pass through each node and be manipulated accordingly.

For most action nodes, data flow is configured when attributes are mapped to the input connection points. For  Gateway nodes, the data flow can be controlled by mapping to the output connection points. This is because the expressions in a gateway provide the logic for which path the data flows, and different paths may require different data to pass through the gateway.

Types of Action Node (move to own page)

The following table summarises the purpose of each type of action node, the types of connections available on an action node and how each node runs.

• Pass-through and Join nodes (only attributes common to all paths leading to the Join can be passed through)

Icon	Description	How it runs	Available Connections
Actionflow See Actionflow Node	Embeds an Actionflow within the current Actionflow.	Once per record	Driving connection
Open Screen See Open Screen Node	Add an action to open a specified screen. If the specified screen contains a start phase button the node can then be connected to a start phase node. The buttons can be mapped to each output of the node to trigger different pathways depending on what the user clicks. For example, this method is used if the process requires confirmation by the user. A confirmation screen can appear with a message 'Are you sure?' with two options Yes - the Actionflow continues to the yes output. No - the Actionflow stops	Once per flow	Driving connection
View See View Node	Add a node for a data view. The Actionflow uses views for additional data to use when processing records.	Once per record	Driving connection  Lookup connection
Calculate See Calculate Node	Add an action to manipulate the data that is passed to the calculate action. In the calculate action, write an expression using one or more of the 115+ functions available in PhixFlow.	Once per record	Driving connection
Gateway See Gateway Node	Add a node to specify decision logic. Gateways control the route that records take as they flow through the Actionflow.	Once per record	Driving connection  Lookup connection
Open URL See Open URL Node	Add an action to open a specified URL.	Once per flow	Driving connection
Save See Save Node	Add a node to save the specified record(s) to its table.	Once per record	Driving connection
Delete	Add a node to delete the specified record(s) from its table.	Once per record	Driving connection
Bulk Delete
Run Analysis See Analysis Node	Runs analysis on the specified tables.	Once per record	Driving connection
HTTP See HTTP Node	Performs an HTTP request.	Once per record	Driving connection
Email See Email Node	Sends an Email to specified recipients.	Once per record	Driving connection
JSON See JSON Node	Handles JSON data and returns record objects as defined by the configuration.	Once per record	Driving connection
For Each
Loop Node See Loop Nodes	Facilitates the ability to loop within an actionflow for tasks such as polling or paging through results.	Once per record	Driving connection
Converge
Start Phase See Phase Node	Starts the phase specified by the user on the node. To add a phase node there must be more than one phase in the actionflow.	Once per flow	Driving connection