Outputs

an action output is 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 view action outputs to view the outputs available from an action click an action in your playbook click configure click the outputs tab all available action outputs are displayed in a tree structure, showing the output schema and properties the outputs tab provides a read only view of all outputs that the action produces you can browse the output structure to understand what data is available from the action use action outputs action outputs are automatically available for use as inputs in other actions within the same playbook you can reference action outputs in several ways reference outputs in expressions use dot notation expressions to reference action outputs $actions actionname result propertyname example if you have an action named "get user" that returns a user object with properties like id, name, and email, you can reference these outputs in another action $actions getuser result id references the user id $actions getuser result name references the user name $actions getuser result email references the user email reference nested properties for nested properties, use dot notation to traverse the object structure $actions actionname result parentproperty childproperty example if an action returns a response object with nested data $actions getdata result response data items\[0] name reference array items to reference specific items in an array output, use array indexing $actions actionname result arrayproperty\[0] // first item $actions actionname result arrayproperty\[ 1] // last item $actions actionname result arrayproperty\[index] // specific index discovered outputs in addition to the base property types, action outputs may return additional properties based on the action or connector you use and the inputs you provide these are the discovered outputs you can discover outputs during action testing for more information about discovering outputs and testing actions, see docid\ xdoxji82d8iulanf8c34h error outputs if your action fails, turbine provides a base level error property type for action outputs the error property type gives you access to any output properties when an error occurs currently, the http native action, script native action, and connectors have this property type this provides a better user experience when testing actions and handling errors you can reference error outputs in the same way as regular outputs $actions actionname result error errormessage $actions actionname result error statuscode for information about what happens to your action outputs if your action fails, see docid\ xdoxji82d8iulanf8c34h