1. Planning#

Functionality#

Before you begin development, you'll want to plan out what triggers and actions to build. If you haven't yet, please read How Zapier Works and set up a few Zaps to get a sense of the user experience.

Building on the Zapier platform is different from other platforms in the sense that you'll be creating discrete triggers and actions instead of defining an entire app's end-to-end user experience.

However, it is similar in the sense that end user experience still matters a lot. Simply pointing triggers and actions at your public API endpoints isn't enough. You'll want to strongly consider which triggers and actions your app will support to start and what the user experience looks like while setting up a Zap that includes your trigger or action.

The most successful integrations on Zapier only have a few (2 or 3) triggers and actions to start. You can always add more over time as users request them. If you need help figuring out what might be useful to your users, you can browse the App Directory for similar apps and see what triggers and actions are supported.

In the sections below, we'll break down how to design a successful integraion on Zapier. These sections contain considerations that you should review prior to getting started and serve as a reference as you build your Zapier integration. We break down the guide into the following sections:

Category Specific Guides#

There are also special considerations you should take if your product is a specific category, like a form app. The guides below describe those edge cases and potential solutions for different types of apps so that the users of your integration have better success building Zaps. This is a work in progress and we will be adding more soon!

↑ Was this documentation useful? Yes No