Orchestration
...
Playbook Inputs
Create and Edit Playbook Inputs
6 min
playbook inputs normalize data coming into the playbook even when coming from multiple triggers your playbook can have multiple playbook inputs configure playbook inputs let's see how we configure inputs create a new playbook or upload an existing playbook, then follow the steps below from the playbook toolbar, click playbook inputs the playbook inputs manager window opens click add a property to view the list of properties available for you to map from property configuration , configure the selected property on the general tab, enter the appropriate data click apply depending on the type of trigger, you may need to map properties to the created playbook inputs, or use dot notation to extract data, and then map the properties edit playbook inputs create a new playbook or upload an existing playbook, then follow the steps below from the playbook toolbar, click playbook inputs the playbook inputs manager window opens to edit, select a property, and click the gear icon the property configuration window opens make your modifications and click apply that was easy! configure concatenation for strings without formats concatenation allows you to add context to a playbook input property turbine currently supports concatenation for the following property type without formatting string concatenation only works with string properties that do not have a format (for example, api keys would not be used) 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, ensure you complete (as needed) configure action inputs configure connector properties select assets now, create a concatenation for strings without formats from action inputs , in the desired property field, click + select a property click playbook inputs add a playbook input 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, for example world! the token and static value text display as string concatenation you have successfully created a string concatenation! see string concatenation use case for an example of executing string concatenation need to make changes to your playbook inputs? go to the next section to see how to apply and remove playbook inputs