1.06 Types of Action Node
Types of Action Node
The following table summarises the purpose of each type of action node, the types of connections available on an action node and how each action node runs.
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. For confirmation screens, see 1.13 Confirmation Message Configuration. | Once per flow | Driving connection |
View See View Node | Add an action to view additional data to use in the Actionflow. Use where the originating screen or component does not include all of the data required by the Actionflow. | Once per record | Driving connection Lookup connection |
Calculate | Add an action to manipulate the data that is passed to the calculate action, or to add text (strings). In the calculate action, write an expression using one or more of the 135+ functions available in PhixFlow. | Once per record | Driving connection |
Gateway See Gateway Node | Add an action 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 an action to save the specified record(s) to its table. | Once per record | Driving connection |
Delete See Delete Node | Add an action to delete the specified record from its table. | Once per record | Driving connection |
Bulk Delete See Bulk Delete Node | Add an action for the bulk deletion of records in a table or to delete all records in a table. | Once per record | Driving connection |
Run Analysis See Analysis Node | Runs analysis on the specified tables. | Once per record | Driving connection |
HTTP See HTTP Node | Performs an HTTP request to an API. | Once per record | Driving connection |
See Email Node | Sends an Email to the specified recipient(s). | Once per record | Driving connection |
JSON See JSON Node | Handles JSON data, returning each JSON node, defined by the configuration, as an attribute. | Once per record | Driving connection |
XML See XML Node | Use to process XML data, and convert it into specific data objects that can be used by PhixFlow for processing. | Once per record | Driving connection |
For Each See For Each Node | Iterates through a set of records or values in an array, performs processing and generates an output record for each value passed in. | Once per record | Driving connection |
Loop Node See Loop Nodes | Provides the ability to loop within an Actionflow for tasks such as polling an API or paging through results returned by an API. | Once per record | Driving connection |
Converge See Converge Node | Converges two paths within an Actionflow. This action node does not merge any records but converges paths together. Only attributes common to all paths leading to the Converge action node will be passed through. | Once per record | Driving connection Lookup connection |
Start Phase See Phase Node | Starts the phase specified by the user on the action node. To add a phase action node there must be more than one phase in the Actionflow. | Once per flow | Driving connection |
Annotation See Annotations | Allows notes to be added to the canvas, explaining the actions or giving more detail on what is happening at each stage of the Actionflow. | N/A | N/A |
Action nodes that interact with recordsets, e.g. View, Save, will ignore any invalid recordsets, except those created in the same Actionflow.