5. Ongoing Support#

This guide only applies to you if you're planning on making your app public.

After your app is Public, several ongoing things may come up.

Adding or changing features to the app#

You may like to add a new trigger or action based on user feedback or improve the existing user experience.

You can do this entirely self serve by following reading about app migration here.

The most important thing is to not make breaking changes. Zapier performs some automated checks to this regard but you'll want to be very careful changing things like:

  1. The data model that is exposed for triggers.
  2. Scripting to transform or add custom logic.

In general it's safe to add something new and dangerous to change existing functionality. We recommend versioning your triggers and actions and hiding legacy versions. This way old Zaps still function but new users can use the new versions.

Bugs and feature requests#

We track bugs and feature requests in a tool called Issues by Zapier, accessible via the Developer Platform. Whenever our support team comes across a bug or a feature request for your app, we'll log it so we can work together on resolving it for our mutual users. Learn more about Zapier Issues.

↑ Was this documentation useful? Yes No
Get Help