---
title: "Variables"
url: https://docs.catalyst.zoho.com/en/pipelines/help/catalyst-pipelines.yaml/build-the-pipeline/variables/
description: "Learn about the Catalyst Pipelines variables in detail, the associated keywords and sample code snippets."
last_updated: 2026-08-28T06:26:16Z
service: Pipelines
type: general
related_links:
  - name: "Configure the Pipeline"
    url: /en/pipelines/help/catalyst-pipelines.yaml/implementation
---

# Variables

# Introduction

A variable is a placeholder value that can be defined at the job level or pipeline level as required. You cannot define a variable at the stage level. 

You can define the required variables for the pipeline as key-value pairs using the `variables` key. 

### Properties of a Variable

<table class="content-table">
        <thead>
            <tr>
                <th>Key</th>
                <th>Value</th>
                <th>is Mandatory</th>
            </tr>
        </thead>
        <tbody>
            <tr>
                <td>Variable Name</td>
                <td>Specify a string value for the variable</td>
                <td>Yes</td>
            </tr>
            </tbody>
</table>

### YAML Code Snippet for Variable

You can declare a variable at the job level in the `catalyst-pipelines.yaml` file using the below syntax:

```yaml
variables:
  target:'app3.1'

```

### Global Variables 

You can define a variable at the pipeline level directly from the console. Refer to [this help page](https://docs.catalyst.zoho.com/en/pipelines/help/catalyst-pipelines.yaml/implementation) to know the exact steps to create a variable. 

> **Note:**

You must mandatorily set a global variable named **CATALYST_TOKEN** and input the token generated from your Catalyst CLI, in case you have used Catalyst CLI in the pipeline execution. To fetch your token, please refer to the steps mentioned in [this help section](https://docs.catalyst.zoho.com/en/cli/v1/cli-options/#--token-lttokengt).

### Access the Variable 

A variable can be accessed by using any of the following methods:

* **`<< variables.{variable_name} >>`** : This can be used to access any variable defined at the job level. 

* **`<< event.{variable_name} >>`** : This can be used to access any variables passed in the event JSON while triggering the pipeline manually from the console. 

* **`<< env.{variable_name} >>`** : This can be used to access variables defined at the pipeline level.