---
title: Create and Edit Playbook Inputs
slug: create-and-edit-playbook-inputs
docTags: 
createdAt: 2025-08-11T11:13:46.000Z
---

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:

1. From the playbook toolbar, click **Playbook Inputs**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/XJrqFpm1rPzaAeWk14dJT_playbook-inputs-link.png" size="72" width="1459" height="405" darkWidth="800" darkHeight="221" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
The **Playbook Inputs Manager** window opens.
:::

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/YQmGQLuZ-7Y_8yQ0XawzE_playbook-inputs-manager.png" size="78" width="1700" height="800" darkWidth="800" darkHeight="376" position="center" indent="2" showCaption="false"}

2. Click **Add a property** to view the list of properties available for you to map.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/wHauecv341doN-d0yRezP_add-a-property.png" size="16" width="200" height="300" darkWidth="800" darkHeight="1200" position="center" indent="2" showCaption="false"}

3. From **Property Configuration**, configure the selected property.
4. On the **GENERAL** tab, enter the appropriate data.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/rdLb33YstGv2S4dvLMgjI_property-configuration-general-tab.png" size="52" width="600" height="700" darkWidth="800" darkHeight="933" position="center" indent="2" showCaption="false"}

4. 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:

1. From the playbook toolbar, click **Playbook Inputs**.
   The **Playbook Inputs Manager** window opens.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/XJrqFpm1rPzaAeWk14dJT_playbook-inputs-link.png" size="56" width="1459" height="405" darkWidth="800" darkHeight="221" position="center" indent="2" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/YQmGQLuZ-7Y_8yQ0XawzE_playbook-inputs-manager.png" size="74" width="1700" height="800" darkWidth="800" darkHeight="376" position="center" indent="2" showCaption="false"}

2. To edit, select a property, and click the gear icon.
   The **Property Configuration** window opens.
3. Make your modifications and click **Apply**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/BGyCqCvN96RDuS_51UhpH_modified-playbook-input-property.png" size="66" width="1700" height="800" darkWidth="800" darkHeight="376" position="center" indent="2" showCaption="false"}

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**

:::hint{type="info"}
Concatenation only works with string properties that do not have a format (for example, API keys would not be used).
:::

:::hint{type="danger"}
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):

1. Configure action inputs
2. Configure connector properties
3. Select assets

Now, create a concatenation for strings without formats:

1. From **Action Inputs**, in the desired property field, click **+ select a property**.

![](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/of_8w4hNbUqX_6V_uTpVC_broadcast-message-input.png)

1. Click **Playbook Inputs**.
2. **Add a playbook input**.
3. Configure a playbook input for the string.

![](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/YkED9bHwPUqfxkXSeQvqw_broadcast-message-pb-input.png)

1. Click **Done**, then select the playbook input you configured.
   The input displays as a token in the appropriate field.

![](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/bpd6z1vo8qsitIUTrwzru_concatenate-token.png)

1. Next to the token, enter text, for example: **world!**
   The token and static value text display as string concatenation.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/91sGLi71nsR64SJheG5aa_concatenate-token-static-text.png" size="64" width="1783" height="769" position="center" indent="2" showCaption="false"}

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.