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.

Hello everybody,

I have 32 zaps in my list which use an older version of the Moco app. I also have 11 zaps which already use the latest Moco app. Editing a zap in order to use the latest Moco version apparently would take quite a bit of time. The problem is that I don’t have that much time during my daily routine.

Now I had the idea to export all zaps into a JSON file and perform a search & replace job on the selected_api and the authentication_id. After that, I would import the JSON file.

I assume everything would get overwritten and would (hopefully) still work as intended. Has anyone ever tried this? Or is there a better way to assign a newer app version to all 32 zaps?

Any help is greatly appreciated!

Thanks,

Sakis

 

 

Hi @Sakis, welcome to the Community!

I think that this would be the easiest way to change the app for a number of Zaps at the same time. One thing to be aware of is that the fields in the new Moco app might be different from the legacy one. Even if they look the same, they may have different names in the code. I’d recommend checking the fields in the new app before going ahead with the export. 

I’ve not tried this myself but assuming that the selected_api and authentication_id fields are correct, I can’t see any reason why it shouldn’t. When you import the json files, they will create new Zaps in a private folder and not overwrite the old ones. 

You can read more about what to expect when you import Zaps in this help guide: Import and Export Zaps in your Team or Company account

 

​I hope that helps, please let us know if you have any questions!

Hi Danvers,

Thanks for your reply! OK, so an import would work and be non-destructive, that’s good news.

I did some rearch on the Moco app but I couldn’t find any helpful information on how to compare fields or the code itself. Can you give me a hint where to search for details?

Thanks,

Sakis

Hi @Sakis 

I’d recommend making a duplicate of an Zap that would need to be updated, then testing the export/update/import of the JSON to see if that works before making changes to the live Zaps.

Terms & Conditions