Private vs public integrations

When building an integration on the Zapier Platform, you must specify the intended audience. The intended audience determines whether the integration will be private or public:

  • Public integration: For public use and accessible to all Zapier customers.
  • Private integration: For personal, internal (e.g. with your team), personal, or controlled-access use.

Both private and public integrations can connect to Zapier’s app directory of over 5000+ integrations. Depending on your intended audience, there will be different features and limitations available to you.

Note: The intended audience is different from your integration’s status. All integrations, regardless of intent, start with a private status. Learn more in Zapier integration review guidelines.

Public integrations

Public integrations are suitable for the following use cases:

  • Connect your product to Zapier for public use
  • Gain exposure from Zapier’s 3 million+ users

By creating a public integration, you’ll have access to these features:

Limitations

If you’re building a public integration, there are specific limitations to be aware of:

Private integrations

Private integrations are suitable for the following use cases:

  • Connect your internal tool or system to Zapier.
  • Extend what you can do with Webhooks or Code steps.
  • Connect your product to Zapier to build workflows for your team.
  • Create an integration for a staging or testing environment.

By creating a private integration:

  • You control who has access to your integration.
  • Your private integration won’t appear within Zapier’s app directory.

Limitations

If you’re building a private integration, there are specific limitations to be aware of:


Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.