Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi, 

I would like to know how can I let users to choose the environment of their zaps

like to have an endpoint that makes API calls to a staging/sandbox environment URL and other for production. 

I don’t want to have different version pointing to different environments, just an option to select the variable URL, like a dropdown list  or something similar when choosing the zapier account. 

Best regards

 

Luis M.

An approach that I think you could take here:

 

  1. Define environment variables for both staging and prod. staging_base_url, prod_base_url, staging_client_id, prod_client_id, etc
  2. Add an input field to your auth configuration in your Zapier integration. Maybe static dropdown with production and staging selections. Or a boolean for staging. Either way it should default to production. 
  3. Now, every place you reference a base url, or other environment variable, you’ll check bundle.inputData.environment (or whatever key you choose) and use a conditional to say if it’s staging use this env variable, if it’s prod use that environment variable. You could build some helper functions to make that easier. If you’re using the UI builder environment you’ll need to use ‘code mode’ pretty much everywhere - and it’s going to be easier to manage your code in the Zapier CLI if you have more than a couple triggers and actions. 

I don’t love this approach if you’re planning on publishing your integration on the Zapier App Directory. I’d like to find a way for regular users to not see that choice. But if you’re building for yourself or your team I think this approach is pretty good.

Terms & Conditions