Integrations can define environment variables that are available when the app’s code executes. They are useful when you have data like an OAuth client ID and secret that you don’t want to commit to source control. Environment variables can also be used as a way to toggle between a staging and production environment during app development and this would be recommended instead of the use of an independent integration for staging purposes.
x
icon to remove variables if needed.Use environment variables in Zapier's API call forms or in custom code
YOUR_KEY
with your actual key: {{process.env.YOUR_KEY}}
Zapier will then replace that variable with the value for that key from your Advanced settings and will use the correct value every time if you change it in the future. You can also reference environment variables in custom code if you switch your API call to code mode.
You can change environment variable values, but not the original keys
key: ENVFLAG / value: staging
{{bundle.authData.env_url}}
throughout the integration to conditionally call the corresponding domain.