Inputs

available in the playbooks, actions are individual capabilities of connectors and interact with external technologies by passing in data via action inputs and then results are available from action outputs you create actions by installing turbine connectors actions can call another playbook interact with external technologies contain inputs and promote outputs you do not need a trigger to add an action to your playbook create actions from your current playbook, click add an action the action window displays to the right of the playbook from action, enter the required title field note the name field auto populates as the same text from the title field click the action drop down list select the desired action click show advanced settings to see the pool drop down menu the $default pool is automatically assigned, but you can select a different pool note you can select a connector as an action, or you can select an existing playbook as an action to nest in your current playbook click configure note actions selections come from the existing connectors tip once you have selected an action, click save at any time after selecting an action from the drop down important! you cannot save without selecting an action you will receive an error notification configure action inputs action inputs are information necessary for the execution of the task action icon meanings icon meaning edit icon this icon is disabled until you create a condition for the action duplicate icon this only duplicates the action delete icon this deletes the entire action add action inputs once you add an action, you can configure action inputs to configure action inputs from action, in the action drop down, select the desired connector click configure on action inputs, the inputs and outputs tabs display based on the selected connector, action inputs auto populates properties under connector action also, the additional options section displays available assets, which are based on the connector the section also includes repeat property options see docid\ qm0dxeh4nzkrhwd fthlw for details assets allow users to create a reusable set of values that can be applied to actions as inputs in playbooks assets can be for a specific connector, or created as a custom asset which can be applied to any action inputs assets are most useful for standardizing and securing configurations tip assets = action configuration templates configure connector properties when configuring an action, the available property types display under connector action depending on the property type, there are different values you can apply the value options are different for string property types and all other types the default value for string property type is dynamic value the default value for other property types is static value what's a dynamic value? a dynamic value for string property types allows you to add context and/or repeats to a playbook property or expression for details, see the configure concatenation for strings without formats sub section and/or docid\ qm0dxeh4nzkrhwd fthlw configure other values for property types the default value for other property types is static value for property types other than string, the drop down menu options are static value , playbook property , or expression , which allow you to enter a static value, apply a playbook property, or create a dot notation expression to configure the connector properties click the property type drop down, then select from static value , playbook property , or expression complete for all required properties click apply select assets connectors have assets assets are pre defined configurations for some input fields required in actions, or you can customize assets to select pre defined assets navigate to the action inputs if you want to apply an existing asset, click the select from available assets menu and select an asset the available asset property fields are auto filled complete any fields that are not auto populated click apply customize assets see docid\ u1k4ogw5ohahrkpbgeua6 for instructions on how to create and configure a custom asset and apply it to a playbook action property types actions have the following input property types property types description string sequence of alphanumeric characters number floating point and integers integer real numbers that do not have a floating point boolean either of the values true or false object structure that contains more properties array ordered list of zero or more elements, each of which may be of any type arrays use square bracket notation with comma separated elements array types arraynumber, arraystring, and arrayobject null empty value, using the word null date iso 8601 date string without time information date & time iso 8601 string with date and time password obfuscated string, the text will not be human readable within the platform code formatted code string configure concatenation for strings without formats concatenation is the ability to add context to a playbook input property turbine currently only has the string property type without formatting concatenation only works with string properties that do not have a format, i e , api keys would not be used with string concatenation the property types date , date & time , and password are string inputs; however , they are formatted therefore, you cannot create a string concatenation using those properties before configuring concatenation for strings without formats, ensure you complete (as needed) configure action inputs configure connector properties select assets now, create a concatenation for strings without formats you need playbook inputs and/or expressions to configure an action input for string concatenation let's begin by creating a playbook input from the action inputs window from action inputs, in the desired property field, click + select a property click playbook inputs warning if you have not added any playbook inputs yet, you will need to click add a playbook input from here, configure a playbook input for the string click done , then select the playbook input you configured the input displays as a token in the appropriate field next to the token, enter text, i e , world! the token and static value text display as string concatenation you have successfully created a string concatenation! see docid\ ohisxftewcg n72 6gve for an example of executing string concatenation add object sub properties the property types object and array have sub properties you can map the sub properties as a static value, playbook property, or dot notation expression to add an object sub property navigate to the action inputs navigate to the object property type now, click add object properties select a sub property from the drop down repeat steps 3 and 4, if desired to add more than one sub property map the property type by selecting from static value , playbook property , or expression the dynamic value option defaults for string property types if desired, you can also change the name of the sub property to enable editing, click in the sub property field and enter a new name now, the new name and selected mapped option display add array sub properties to add an array sub property navigate to the action inputs depending on the connector, array types might be available navigate to the array property type click add array items click add an item click add a dynamic value field displays that allows you to add context and/or select a property repeat steps 4–6, if desired, to add more than one sub property configure the array sub property click apply clear a sub property entry to clear the information for the sub property click the clear value icon to save the changes, click apply delete a sub property entry to delete the information for the sub property click the delete vertical ellipsis to save the changes, click apply