Skip to main content
A configuration is a set of key-value pairs attached to a job and resolved at run time: the automation reads a key and gets the current value. Credentials for the target system are the most common use, which keeps them out of the automation itself and out of its history.

Using configurations

Create a configuration in the dashboard under Configurations, add your properties, and attach it to the job. The job page shows which configuration a job uses. Change a value and the next run picks it up; nothing needs to be rebuilt or retaught. Configurations also select the environment. A job pointed at a staging configuration runs against your staging system; swap the configuration and the same job runs against production. For login challenges that need a code, see 2FA / OTP.
Change a value in one place and every run after picks it up. Credentials never live in the automation itself.