# Create a RunBook Input Parameter

Parameters are the input key:value pairs that can be submitted with your xRunBook in order to run. Let's walk through the steps to create a Parameter for your xRunBook.

## Add Parameter

In this step we will define the key for an input (in the example below, we create a `customer` input key).  You can imagine that you might run a xRunBook with the key:value pair `customer: John Doe.`

{% hint style="info" %}
As a best practice, use snake case for parameter names.
{% endhint %}

To add a parameter to your xRunBook, click the Parameters button to reveal the drop down.&#x20;

![Adding a \`customer\` input parameter.](/files/9HPqjcj8zUs8lYp2VfCj)

Fill in the required information and click `CREATE`. Once created, the parameter is available to be used as a Python variable of the same name. You can use this in code for custom Actions that you create, or as arguments to the Actions you are using.

{% embed url="<https://youtu.be/08L2CpWGWdg>" %}
Example of adding an input parameter to a RunBook and Reusing it in Actions.
{% endembed %}

## Input Types

* string
* number
* boolean
* array
* object
* secret (string obfuscated with \*)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.unskript.com/unskript-documentation/runbooks/xrunbooks/create-a-parameter.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
