As part of the migrations to the latest Zapier Platform some app triggers and actions are being deprecated. You will have received an email notification from us with details of any triggers or actions that are affected. In this article you’ll find answers to common questions and how to see if your Zap is using a deprecated triggers and/or actions.
What is a deprecated trigger/action?
The deprecated stage refers to the period when an app is no longer supported or maintained. This means that the app has a specific end-of-life date after which it will no longer work. Any Zaps using deprecated versions will turn off on that date. Until then, the app will not receive updates, bug fixes, or technical support. Zapier will notify you by email whenever a version is deprecated.
Why are these deprecations taking place?
Apps are being upgraded to run on the latest version of the Zapier Platform to improve performance. During the migration certain triggers and actions with low usage rates are being deprecated. You can learn more about the migration here: Migrating apps to the latest Zapier Platform - what you need to know
When will the deprecations take effect?
From Dec 15th, 2024 onwards any deprecated triggers and actions will cease to function. You will need to update any potentially affected Zaps before then to ensure that your existing workflows are not impacted.
If a trigger is deprecated will the entire Zap break or need to be recreated?
Yes, for deprecated triggers these will automatically be removed from the Zap and will need to be replaced with an alternative trigger.
Is it possible to see all the Zaps that are impacted by this change?
Yes, you can filter the list of Zaps here by app to review each affected Zap manually. From there you can click through into each potentially affected Zap to check and resolve any issues:
Are there any workarounds for triggers that have been removed completely?
Depending on the app you may be able to subscribe to webhook notifications using the Webhooks by Zapier app. You can learn more about how to set up webhook triggers here:
Alternatively, if you are able to receive email notifications from the app containing details of the event that you wish to trigger a Zap on you could trigger on those emails instead. For this approach you would set up an automatic forwarding rule in your email provider to forward the email notifications to an app like Email Parser by Zapier which will extract the information from it. Then, you’d set the Zap to trigger from those emails and carry out any necessary actions.
You can learn more about this approach here: Trigger Zaps from new parsed emails.
Are there any workarounds for actions that have been removed completely?
Yes, in some cases it may be possible to use a Custom Action or API Request action. If Custom action or API Request action option is not available for the app, and the app’s API supports basic authentication methods, then the Webhooks by Zapier app could be used instead. See our Send webhooks in Zaps guide for more details.
Will these deprecated triggers and actions continue to work beyond their deprecation or can they be reinstated?
No, any Zaps still using deprecated triggers/actions will continue to function up until Dec 15th, 2024. From this date, any Zaps using deprecated triggers/actions will cease to work and will start returning errors.
Can I put in a feature request for a deprecated trigger or action to be reinstated?
Of course! To do that please contact our Support team here and they’ll ensure a feature request is opened up on your behalf. From there we will continue to track interest in having the previously available trigger/action re-created.
Will any of the functionality of the deprecated triggers/actions still be available in the new app?
Not at present but you can always reach out to our Support team to put in a feature request for the deprecated functionality to be restored.
Thanks for your understanding on these upcoming changes. If you run into any issues updating your Zaps ahead of the migration please reach out to us in the Community here or contact our Support team directly and we’ll be happy to assist. 