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.

As a developer, what approaches do y'all favour for testing an upcoming Zapier App version?

Some options come to mind:

  1. Release a new private version, make the changes and point URLs to a testing backend server. Check everything works. Once happy, point URLs to live server again and promote version.

  2. Create a Zapier App which is essentially a copy of the Production one. This app is permanently pointing to a testing backend server. Drawback: it's hard to ensure they are in sync. Updating settings is a manual error-prone process.

  3. Use Zapier CLI instead of the Web Builder and rely on unit tests (From Zapier CLI i just know what i read from the docs, haven't tried it yet).

Anyways, i am curious about other people's recommendations. Floor is open for discussion :)

Terms & Conditions