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.

I’m looking into integration maintenance over time and it’s not clear from the documentation if the end user of the Zap can upgrade their Zap themselves to use specific or “promoted” integration version?

The scenario described in the migration of users shows how we as developers can automatically migrate users from one version to another. What I’m looking into is possibly leaving it up to the end user to decide and migrate themselves. Example usecase is following: new integration comes with additional fields in a trigger but to get those additional fields working the user would need to check if their self-hosted API is up to date (some work on user’s end).

Thanks in advance!

Hi @naz 

Typically users that have zaps built and switched on with older versions of integrations will be left that way - but if they switch those zaps off, they won’t be able to switch back on without migrating. Ditto for making copies of those zaps or trying to edit them.

Terms & Conditions