Actions

term definition characteristics action actions are individual capabilities of connectors that enable users to create automation workflows interacting with external technologies they define what a connector can do, such as retrieving data, sending requests, or managing assets on the other hand, there are prebuilt actions included by default within a connector they offer a streamlined, customized configuration experience tailored for optimal performance in swimlane turbine, requiring no manual setup by the user for more information refer to docid\ pjvlixcu3srwtkilu vtm pass/process data inputs \ results available in outputs \ functionality options conditions, loops, retries, repeats, discovered outputs, testing overview actions are individual capabilities of connectors that enable you to create automation workflows interacting with external technologies actions define what a connector can do, such as retrieving data, sending requests, or managing assets native actions are prebuilt actions included by default within turbine they offer a streamlined, customized configuration experience tailored for optimal performance, requiring no manual setup native actions include http request, script, transform data, condition, loop, parallel, create record, delete record, update record, search records, create variables, and update variables for more information about individual native actions, see docid\ pjvlixcu3srwtkilu vtm add actions to your playbook to add an action to your playbook open the add panel on the left side of the playbook canvas browse or search for the desired action from the available connectors and native actions native actions appear at the bottom of the add panel connector actions are organized by vendor/connector drag the action from the add panel drop the action onto the canvas drop onto a drop zone (indicated by a plus icon) to add it to the flow drop onto an edge to insert it between existing actions drop onto a node to connect it after that action after dropping, the action appears on the canvas and the action details panel automatically displays to the right of the playbook you do not need a trigger to add an action to your playbook for detailed information about adding actions, including how to use the add panel, see docid dy2dffdex99ri 0sunoz > create actions configure actions after adding an action to your playbook, configure it with inputs, outputs, assets, and other settings open the configure dialog to configure action inputs and outputs, open the configure dialog in one of two ways from the action details panel in the data section, click configure from the canvas click the edit icon that appears when you hover over an action node the configure dialog opens with inputs and outputs tabs, where you can configure the action properties the configure dialog appearance and available options vary depending on the action type for example, native actions like create variables, update variables, http request, script, transform data, condition, loop, and record actions each have their own specialized configuration dialogs configure action inputs action inputs are information necessary for the execution of the task configure action inputs based on the selected connector or action type for detailed information about configuring action inputs, including action property types configuring connector properties selecting assets configuring concatenation for strings adding object and array sub properties see docid dy2dffdex99ri 0sunoz configure action outputs action outputs are the response and/or result(s) from a connector technology action outputs can be applied as inputs for other actions within your playbook, or promoted for use outside of the current playbook for detailed information about viewing and promoting action outputs, see docid 9nhdhohxo hwork orgfs action features actions support various features that enhance automation workflows conditions control when actions execute based on conditions loops repeat actions for multiple items retries automatically retry failed actions based on conditions and limits discovered outputs discover additional outputs during action testing testing test actions individually before running the entire playbook related topics docid dy2dffdex99ri 0sunoz configure action inputs and properties docid 9nhdhohxo hwork orgfs view and promote action outputs docid\ pjvlixcu3srwtkilu vtm learn about individual native actions docid\ noefia6viemlogfrjdbi0 configure action retries docid\ xdoxji82d8iulanf8c34h test actions and discover outputs