Skip to content
Switch branches/tags
Go to file

Auth0 Deploy CLI

Auth0 supports continuous integration and deployment (CI/CD) of Auth0 Tenants through our source control extensions and integration into existing CI/CD pipelines by using this auth0-deploy-cli tool.

The auth0-deploy-cli tool supports the importing and exporting of Auth0 Tenant configuration data.

Supported Features

  • Supported Auth0 Objects
    • Tenant Settings
    • Rules (Including Secrets/Settings)
    • Hooks
    • Connections
    • Custom Databases
    • Clients / Applications
    • Resource Servers (APIs)
    • Pages
    • Email Templates and Provider
    • Guardian Settings
  • Configuration options
    • Defined Directory Structure
    • YAML Configuration
    • Programmatically
  • Environment Variable Replacements

Before you begin

  • This tool can be destructive to your Auth0 tenant. Please ensure you have read the documentation and tested the tool on a development tenant before using it in production.
  • Entities created using this tool may share user data with or receive user data from 3rd parties. Please see the documentation for the individual Management endpoints for details.


Check our migration guides to see if you need to do anything when upgrading here.


General Install

npm i -g auth0-deploy-cli


⚠️ Node.js version 8 or later is required to run this tool since v5.0.0.

For this tool to function, it must be authorized to the Auth0 Management API. You can do this by creating an application in your Auth0 service that has access to the management API with the following scopes before.

Use the Auth0 Deploy CLI Extension to create the application. At the bottom of the README are instructions for doing this by hand instead.

If the extension did not create the right scopes, confirm the following:

  1. Navigate to your application that was created for the deploy cli, typically named auth0-deploy-cli-extension.
  2. Ensure the Application type is Machine to Machine.
  3. Refresh the page and an APIs tab should appear on the client.
  4. On the APIs tab, on Auth0 Management API click the drop-down (right arrow) to show the list of permissions.
  5. Ensure the following scopes below are selected:


  • read:client_grants
  • create:client_grants
  • delete:client_grants
  • update:client_grants
  • read:clients
  • update:clients
  • delete:clients
  • create:clients
  • read:client_keys
  • update:client_keys
  • delete:client_keys
  • create:client_keys
  • read:connections
  • update:connections
  • delete:connections
  • create:connections
  • read:resource_servers
  • update:resource_servers
  • delete:resource_servers
  • create:resource_servers
  • read:rules
  • update:rules
  • delete:rules
  • create:rules
  • read:hooks
  • update:hooks
  • delete:hooks
  • create:hooks
  • read:rules_configs
  • update:rules_configs
  • delete:rules_configs
  • read:email_provider
  • update:email_provider
  • delete:email_provider
  • create:email_provider
  • read:tenant_settings
  • update:tenant_settings
  • read:grants
  • delete:grants
  • read:guardian_factors
  • update:guardian_factors
  • read:mfa_policies
  • update:mfa_policies
  • read:email_templates
  • create:email_templates
  • update:email_templates
  • read:roles
  • update:roles
  • delete:roles
  • create:roles
  • read:prompts
  • update:prompts
  • read:branding
  • update:branding


This tool supports multiple methods to import and export Auth0 configuration objects.

Option 1 - Predefined Directory Structure

Please refer to Directory README for usage instructions and examples.

Option 2 - YAML configuration file

Please refer to YAML README for usage instructions and examples.

Option 3 - Called Programmatically

The tool can be called programmatically. Please see below for an example.

import { deploy, dump } from 'auth0-deploy-cli';

const config = {
  AUTH0_DOMAIN: process.env.AUTH0_DOMAIN,

// Export Tenant Config
  output_folder: 'path/to/directory', // Output directory
  base_path: basePath, // Allow to override basepath, if not take from input_file
  config_file: configFile, // Option to a config json
  config: configObj, // Option to sent in json as object
  export_ids: exportIds, // Export the identifier field for each object type
  secret // Optionally pass in auth0 client secret seperate from config
  .then(() => console.log('yey export was successful'))
  .catch(err => console.log(`Oh no, something went wrong. Error: ${err}`));

// Import tenant config
  input_file: 'path/to/yaml/or/directory', // Input file for directory, change to .yaml for YAML
  base_path: basePath, // Allow to override basepath, if not take from input_file
  config_file: configFile, // Option to a config json
  config: configObj, // Option to sent in json as object
  env, // Allow env variable mappings from process.env
  secret // Optionally pass in auth0 client secret seperate from config
  .then(() => console.log('yey deploy was successful'))
  .catch(err => console.log(`Oh no, something went wrong. Error: ${err}`));


The auth0-deploy-cli tool leverages the Auth0 Management API passing through objects for creates, updates and deletions.

You may experience Bad Request and Payload validation errors. These errors are returned from the Auth0 Management API, and usually mean the object has attributes which are not writable or no longer available (legacy). This can happen when exporting from an older Auth0 tenant and importing into a newly created tenant. In this scenario, you may need to update your configuration to support the new object format. See #45 for a potential fix.

CLI Options

The following options are supported by the cli.

a0deploy --help

Auth0 Deploy CLI

 a0deploy import     Deploy Configuration
 a0deploy export     Export Auth0 Tenant Configuration

 --help               Show help  [boolean]
 --version            Show version number  [boolean]
 --debug, -d          Dump extra debug information.  [string] [default: false]
 --proxy_url, -p      A url for proxying requests, only set this if you are behind a proxy. [string]

 a0deploy export -c config.json -f yaml -o path/to/export       Dump Auth0 config to folder in YAML format
 a0deploy export -c config.json -f directory -o path/to/export  Dump Auth0 config to folder in directory format
 a0deploy import -c config.json -i tenant.yaml                  Deploy Auth0 via YAML
 a0deploy import -c config.json -i path/to/files                Deploy Auth0 via Path

See README ( for more in-depth information on configuration and setup.

Recommended Approach/Best Practices

The recommended approach for utilizing this CLI is to incorporate it into your build system. Create a repository to store your deploy configuration, then create a set of configuration files for each environment. On your continuous integration server, have a deploy build for each environment. This deploy build should update a local copy of the deploy configuration repository, then run the CLI to deploy it to that environment. Read on for more detailed information.

Auth0 Tenant layout

The recommended approach is to have a different Auth0 tenant/account for each environment. For example: fabrikam-dev, fabrikam-uat, fabrikam-staging, and fabrikam-prod.

Your Deploy Configuration Repository

Your configuration repository should contain the files as described in the selected option (Directory or YAML)

You should have a branch for each tenant/account. This allows you to make changes to dev, but not deploy them until you merge. With this setup, you can have each environment have a CI task that automatically deploys the changes to its target environment when the branch is updated with the latest.

So your flow would be as follows: dev changes are tested, then merged to UAT, once tested they are merged to staging, once staging is tested they are merged to prod.

You may want to set your prod to only deploy when triggered manually.

Your CI server configuration

Your CI server should have a different deploy task and config for each environment. Since each tenant/account will need to have the auth0-deploy-cli-extension installed in it with a different domain, client ID, and secret, this has to happen anyway and will avoid accidentally deploying to the wrong environment.

The deploy task should follow these steps:

  1. Update the local repo to the latest. (each environment should have its own copy of the repo set to its own branch)
  2. If there are changes, call a0deploy
  3. Run a suite of tests to confirm configuration is working
  4. Optional: merge to next branch

Use keyword mappings to handle differences between the environments

You should not have to store differences between environments in the Deploy Configuration Repository. Use the keyword mappings to allow the repository to be environment agnostic, and instead store the differences in the separate config.json files for each environment that are stored on the CI server.

Make sure to use unique application names

When exporting certain configurations like the applications enabled for a certain connection or the IdP-Initiated settings for a SAML connection, the CLI tool will convert client IDs into client names and convert those client names back into client IDs when importing configurations. Because of this, it's importanting that you keep your application names unique.

This mapping to client names helps to make a tenant configuration independent of the actual client IDs assigned on a deploy.

Other Helpful Topics

To test locally

Clone the GitHub repo and install globally

git clone
cd auth0-deploy-cli
npm install
npm run test

To Create Client Application by Hand

  1. log into your dashboard
  2. click the applications tab
  3. click the "Create Application" button
    1. Name it something like "Deploy Client"
    2. Select Machine-to-Machine as the application type
    3. Click Create
  4. Use the "Select an API" dropdown to choose: "Auth0 Management API"
  5. Select the scopes defined in the section above
  6. Click Authorize

Known issues





A node CLI that can be used to easily integrate configuration deploy with your build scripts.




No packages published