---
updatedAt: 2026-05-28T09:48:58.000Z
agentTools:
  projectIndex: https://help.zluri.com/llms.txt
---

# Create Variables and Dynamic Inputs

Variables and dynamic inputs

## Variables

Variables represent dynamic elements that change during each playbook run. These elements allow playbooks to adapt to different users, applications, or execution contexts.

For example, a Slack playbook may include an action to send an email to a new joiner after access is granted. Each new joiner has a different name, department, and email address. Variables insert this information dynamically instead of relying on hardcoded values.

Variables act as placeholders and fetch user-specific or context-specific data during execution. Common use cases include inserting names, departments, roles, or email addresses into actions.

Dynamic placeholders follow the format `{{entity.attribute}}`.

Examples:

* `{{user.first_name}}` inserts the user’s first name
* `{{user.department}}` inserts the user’s department

This approach improves playbook flexibility, reuse, and accuracy across automation workflows.

## Variables location

1. Open the **Playbook** tab from the onboarding workflow landing page.

   <Image align="center" alt="Variables_playbook page.png" src="https://files.readme.io/dd2567aa009c076ecb80e79da47917af651868039367107f7779b42c8112bfa8-Variables_playbook_page.png" />

2. Open the <Anchor label="playbook configuration" target="_blank" href="https://help.zluri.com/docs/understanding-playbook-builder">playbook configuration</Anchor> page.

   <Image align="center" alt="Playbooks_creatimg new variable.gif" src="https://files.readme.io/ebdad7fb3fa0ee62dc6aca095745d0073baf04ca129d359a45f4b0c452cad7d9-Playbooks_creatimg_new_variable.gif" />

3. Use the variable icons highlighted in blue within the left-side panel.

   <Image align="center" alt="Variable_ icon.png" src="https://files.readme.io/a653d9dd08c0e1b974c7911250084a3842c918531da8bb26c81310a913afa476-Variable__icon.png" />

4. Apply variables to notifications, emails, or access rules without hardcoding values.

   <Image align="center" alt="Variable_create variable.png" src="https://files.readme.io/47d6a87fe49e479304255de1db341616e765af5a59954e31c868d63afe6741c0-Variable_create_variable.png" />

## Object types

Playbooks run across multiple modules and external integrations. The entities responsible for triggering playbooks are referred to as **object types**.

Variables support the following object types:

### Access Request

Used during execution from an access request workflow. Request-related fields such as role, license, or user ID pass into the playbook through the **Trigger Playbook** action.

### Access Reviews

Used during execution from an access review workflow. Review-related data such as reviewer, review action, or review comment passes into the playbook through the **Trigger Playbook** action.

### Text

Used for passing data from external systems such as ITSM tools or automation platforms.

For example, an onboarding ticket created in ServiceNow can pass a ticket ID into a Zluri playbook using the Text object type. The playbook updates the ticket automatically after provisioning completes, enabling tracking across systems.

## Dynamic inputs

Dynamic inputs represent user-based and application-based attributes. These attributes update automatically based on the selected user and application during workflow execution.

For example, an Azure AD workflow action may assign a department value to a user. Static department values limit reuse across teams. Dynamic inputs insert the user’s department dynamically during execution.

Example:

* `{{user.user_department_name}}`

## Components of a dynamic input

Each dynamic input includes two components:

### Entity

Represents the source object. In Azure AD workflows, common entities include **user** and **application**.

### Attribute

Represents the field associated with the entity.

### Dynamic input format

`{{entity.attribute}}`

Example:

* `{{user.user_department_name}}`

## Allowed dynamic inputs

| Entity | Attribute                      | Dynamic input                          | Description               |
| ------ | ------------------------------ | -------------------------------------- | ------------------------- |
| user   | user\_email                    | `{{user.user_email}}`                  | Fetches user email        |
| user   | user\_name                     | `{{user.user_name}}`                   | Fetches user name         |
| user   | user\_designation              | `{{user.user_designation}}`            | Fetches designation       |
| user   | user\_status                   | `{{user.user_status}}`                 | Fetches status            |
| user   | user\_role                     | `{{user.user_role}}`                   | Fetches role              |
| user   | user\_department\_name         | `{{user.user_department_name}}`        | Fetches department        |
| user   | user\_reporting\_manager\_name | `{{user.user_reporting_manager_name}}` | Fetches reporting manager |
| app    | app\_status                    | `{{app.app_status}}`                   | Fetches app status        |
| app    | app\_name                      | `{{app.app_name}}`                     | Fetches app name          |
| app    | app\_owner\_name               | `{{app.app_owner_name}}`               | Fetches app owner         |
| app    | app\_owner\_email              | `{{app.app_owner_email}}`              | Fetches app owner email   |
| app    | app\_financial\_owner\_name    | `{{app.app_financial_owner_name}}`     | Fetches financial owner   |

## Custom dynamic inputs

Custom dynamic inputs support user fields defined in Zluri.

Format:

```
{{user.custom_field.name}}
```

Example:

```
{{user.custom_field.location_id}}
```

Custom dynamic inputs currently support **Text** field types only.

### Example 1: Dynamic inputs in manual actions

Manual actions require configuration of the task **Title** and **Description**. These fields form the email notification sent to the task assignee.

### Setup

* Open onboarding or offboarding workflows.
* Create a new workflow or open an existing playbook.

### New workflow configuration

* Add an application (example: 366 Degrees).
* Select **Create manual task**.
* Select a manual task (example: Add user).
* Populate the **Title** and **Description** fields using dynamic inputs from the supported variables list.

<Image align="center" alt="366 degree.png" src="https://files.readme.io/951d438c73cefdfa6756390678382c208e1f81dc6a154a191a6839d640dbfa4e-366_degree.png" />

**Example**

The following values demonstrate use of dynamic inputs in the task fields:

* **Title**:

  Add `{{user.user_name}}` in `{{app.app_name}}`

* **Description**:

  Add `{{user.user_name}}` (email: `{{user.user_email}}`) to `{{app.app_name}}` with role `{{user.user_role}}`, designation `{{user.user_designation}}`, and department `{{user.user_department_name}}`. Notify `{{user.user_reporting_manager_name}}` after completion.

<Image align="center" alt="366 degree add user screen.png" src="https://files.readme.io/2159203700393f0db71bd8becbdcfa2448588efaf6662834ecf90d06886aefaf-366_degree_add_user_screen.png" />

### Existing playbooks

* Open a manual task for an application (example: Add user).
* Update the **Title** and **Description** fields using dynamic inputs from the supported variables list.
* Save the playbook.

**Example values**

* **Title**:

  Add `{{user.user_name}}` in `{{app.app_name}}`

* **Description**:

  Add `{{user.user_name}}` (email: `{{user.user_email}}`) to `{{app.app_name}}` with role `{{user.user_role}}`, designation `{{user.user_designation}}`, and department `{{user.user_department_name}}`. Notify `{{user.user_reporting_manager_name}}` after completion.

**Notes**

* Use double curly braces for all dynamic inputs in the format `{{entity.attribute}}`.

  *Example:* `{{user.user_name}}`

* Field values resolve dynamically based on the selected user during workflow execution.

**Example**

If a user’s department in Zluri is **Product**, the value of `{{user.user_department_name}}` resolves to **Product** during the workflow run.

### Example 2: Dynamic inputs in automated actions

Automated actions support dynamic inputs in user-related free-text fields.

### Setup

* Open onboarding or offboarding workflows.
* Create a new workflow or open an existing playbook.

### New workflow configuration

* Add an application (example: Azure AD).
* Select an action with a user-related free-text field (example: Add department name).
* Populate the field using a dynamic input from the supported variables list.

  <Image align="center" alt="Azure AD 2.png" src="https://files.readme.io/75d8fa1d9ab321214f148b7baf1946ce3eecf2aad5e3ae305912992c26002485-Azure_AD_2.png" />

  **Example**

  The **Department** field uses the dynamic input for user department, enabling automatic updates based on the selected user during execution.

  <Image align="center" alt="Azure AD 1.png" src="https://files.readme.io/ba91bbe0e3524ef9b9474db58b8a297ea65498daa03337d292c176c7f39d7ad7-Azure_AD_1.png" />

### Existing playbooks

* Open an action in the playbook with a user-related free-text field (example: Add department name).
* Populate the field using a dynamic input from the supported variables list.
* Save the playbook.

**Note**

Always format dynamic inputs using double curly braces in the format `{{entity.attribute}}`.

*Example:* `{{user.user_name}}`

Field values resolve dynamically based on the selected user during workflow execution.

**Example**

If a user’s department in Zluri is **Product**, the value of `{{user.user_department_name}}` resolves to **Product** for that workflow run.

### Example 3: Dynamic inputs in Zluri actions . HTTP request

Dynamic inputs are supported in Zluri HTTP request actions across URL, headers, and request body fields.

### Setup

* Open onboarding or offboarding workflows.
* Create a new workflow or open an existing playbook.

### New workflow configuration

* Select **Zluri Actions**.
* Select **Choose action > Make an HTTP Request**.
* Populate the **URL**, **Headers**, and **Values** fields using dynamic inputs from the supported variables list.

**Example**

* **URL**

  Insert a dynamic input in the request parameter to update values during each workflow run.

  ```
  https://api.github.com/users/{{user.user_name}}
  ```

This configuration updates the request dynamically based on the selected user during execution.

<Image align="center" alt="Make an http request.png" src="https://files.readme.io/2c5d38e92f8e9ce4fc76ccb8d958398d78058988ce671c1762903bc66ea1d43b-Make_an_http_request.png" />

**Headers**

Add request headers as specified in the GitHub API documentation. Headers can be copied from the cURL command and pasted into Postman to extract the required values.

<Image align="center" alt="import.png" src="https://files.readme.io/be7e31258949c0a48266a0fd1fd08dd27eccfff09bce5bea3b81eaf99933a134-import.png" />

### Existing playbooks

* Select **Zluri Actions > Make an HTTP Request**.
* Populate the **URL**, **Headers**, and **Values** fields using dynamic inputs from the supported variables list.
* Save the playbook.

**Example configuration**

* **URL**

  Insert a dynamic input into the request parameter to update values during each workflow run.

  ```
  https://api.github.com/users/{{user.user_name}}
  ```

* **Headers**

  Add request headers as specified in the GitHub API documentation. Headers can be copied from the cURL command and extracted using tools such as Postman.

**Note**

Always format dynamic inputs using double curly braces in the format `{{entity.attribute}}`.

*Example:* `{{user.user_name}}`

Field values resolve dynamically based on the selected user and application during workflow execution.

**Example**

In the URL `https://api.github.com/users/{{user.user_name}}`, the `{{user.user_name}}` parameter resolves to the username of the user associated with the workflow run.

<br />