I’ve been using a GitHub “New Issue” <on_repo> trigger, but just got an email saying that trigger will be deprecated on Dec 15, 2024, and I should “Update your Zap steps to the non-legacy version of the deprecated event (trigger/action), if available”
Unfortunately, there was no detail available about where to discover a corresponding “non-legacy version”. Does anyone know what steps I should take to create a new Zap with similar functionalty?
Best answer by Troy TessaloneBest answer by Troy Tessalone
Help link about updating Zap app versions: https://help.zapier.com/hc/en-us/articles/18755649454989-Update-to-the-latest-app-version-in-Zaps
+14Hi
Go to the Zap trigger step “Setup” tab and try searching for ‘New Issue’, then select the non-legacy version.
Thanks! I tried using the copilot entry to suggest a Zap, and it was able to find “Gitub (1.0.2)” which is different from my existing “Github” trigger name.
But I’m not sure if that new “Github (1.0.2)” trigger name (app name?) will survive past December 15. After testing and publishing the new Zap, it displayed a message: “Your Zap is on and using version "v1". Are all v1 apps planning to be deprecated?
Jason
+14Help link about updating Zap app versions: https://help.zapier.com/hc/en-us/articles/18755649454989-Update-to-the-latest-app-version-in-Zaps
Thanks! Now I get it - the “V1” was the version of my Zap, not the API it used :)
Going forward, I’ll rely on the status icon to guide me.
+6That’s awesome
If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
