Skip to content


Variables enable you to store and reuse non-sensitive bits of data, such as configuration information. Variables are named, mutable string values, much like environment variables. Variables are scoped to a Prefect server instance or a single workspace in Prefect Cloud.

Variables can be created or modified at any time, but are intended for values with infrequent writes and frequent reads. Variable values may be cached for quicker retrieval.

While variable values are most commonly loaded during flow runtime, they can be loaded in other contexts, at any time, such that they can be used to pass configuration information to Prefect configuration files, such as deployment steps.

Variables are not Encrypted

Using variables to store sensitive information, such as credentials, is not recommended. Instead, use Secret blocks to store and access sensitive information.

Managing variables

You can create, read, edit and delete variables via the Prefect UI, API, and CLI. Names must adhere to traditional variable naming conventions:

  • Have no more than 255 characters.
  • Only contain lowercase alphanumeric characters ([a-z], [0-9]) or underscores (_). Spaces are not allowed.
  • be unique.

Values must:

  • have less than or equal to 5000 characters.

Optionally, you can add tags to the variable.

Via the Prefect UI

You can see all the variables in your Prefect server instance or Prefect Cloud workspace on the Variables page of the Prefect UI. Both the name and value of all variables are visible to anyone with access to the server or workspace.

To create a new variable, select the + button next to the header of the Variables page. Enter the name and value of the variable.


Via the REST API

Variables can be created and deleted via the REST API. You can also set and get variables via the API with either the variable name or ID. See the REST reference for more information.

Via the CLI

You can list, inspect, and delete variables via the command line interface with the prefect variable ls, prefect variable inspect <name>, and prefect variable delete <name> commands, respectively.

Accessing variables

In addition to the UI and API, variables can be referenced in code and in certain Prefect configuration files.

In Python code

You can access any variable via the Python SDK via the Variable.get() method. If you attempt to reference a variable that does not exist, the method will return None. You can create variables via the Python SDK with the Variable.set() method. Note that if a variable of the same name exists, you'll need to pass overwrite=True.

from prefect.variables import Variable

# setting the variable
variable = Variable.set(name="the_answer", value="42")

# getting from a synchronous context
answer = Variable.get('the_answer')
# 42

# getting from an asynchronous context
answer = await Variable.get('the_answer')
# 42

# getting without a default value
answer = Variable.get('not_the_answer')
# None

# getting with a default value
answer = Variable.get('not_the_answer', default='42')
# 42

# using `overwrite=True`
answer = Variable.get('the_answer')
answer = Variable.set(name="the_answer", value="43", overwrite=True)

In prefect.yaml deployment steps

In .yaml files, variables are denoted by quotes and double curly brackets, like so: "{{ prefect.variables.my_variable }}". You can use variables to templatize deployment steps by referencing them in the prefect.yaml file used to create deployments. For example, you could pass a variable in to specify a branch for a git repo in a deployment pull step:

- prefect.deployments.steps.git_clone:
    branch: "{{ prefect.variables.deployment_branch }}"

The deployment_branch variable will be evaluated at runtime for the deployed flow, allowing changes to be made to variables used in a pull action without updating a deployment directly.