How to Get Listed in the Zapier App Directory

To get listed in the Zapier App Directory, you build a private integration on the Zapier Developer Platform and get at least 3 users running live Zaps with it. Every visible trigger, search and action needs a live Zap with a successful run. Then you submit it for review from the Publish page. A Zapier developer contacts you within a week with anything still missing. Once approved, the integration appears in the App Directory with a Beta tag, stays in beta for 90 days, and then becomes public and joins Zapier's Partner Program (Zapier's publishing guide). Publishing is free. Approval is Zapier's decision.

Can your app be listed?

Check this first. Some integrations can never go public, however good the code is. From Zapier's publishing requirements:

• You own the API, or the API owner hired you. Developers who work for the company that owns the API, or are contracted by it, can go public. If you build on a public API you don't own, the integration can only stay private. Zapier checks ownership largely by email domain.
• The app is publicly launched. It can't be invite-only or in beta.
• It uses production endpoints over HTTPS. Integrations that use sandbox, test or dev endpoints won't be published.
• The API is documented. Its docs have to cover all endpoints, and you link them in your submission.
• It's in English. All user-facing text has to be in English. The data your API sends and receives can be in any language.
• It isn't prohibited. No financial transactions or payment processing, no apps from competitors of Zapier or sanctioned countries, nothing misleading or objectionable.
• It isn't a duplicate. Zapier allows one public integration per app. If one already exists for your app, update that one instead of submitting a new one.

If you don't meet these, a private integration is still useful. You can share it with your own users, and it doesn't need to pass validation.

1. Build a private integration

Every Zapier integration starts private. You build it in the Platform UI, a browser editor, or with the Platform CLI in your own codebase. Both run on the same Developer Platform. Zapier doesn't import OpenAPI specs, so if your API has one, see how to generate a Zapier integration from your OpenAPI spec for what you can generate and what you finish by hand.

Credentials go in the authentication setup only. Zapier won't publish integrations that ask for credentials inside a trigger, action or search. Don't hard-code API keys or client secrets either.

2. Get 3 users with live Zaps

This is the step most teams underestimate. Zapier's integration checks block publishing until these pass:

• S001: 3 users with a live Zap. At least 3 users must have a live Zap that uses your integration. "Live" means the Zap is on and has at least one successful run in recent history.
• S002: one live Zap for each trigger, search and action. Every visible one needs a live Zap that shows it works.
• T001: one successful Zap run for each trigger, search and action. Zapier checks this in the Zap History of the integration's admins, so build these test Zaps in admin accounts.
• A001: a connected account. At least one connected account, to show auth works.

To get users, share the private integration from Manage > Sharing in the Platform UI (Zapier's sharing docs). You can:

• Invite by email. You can invite up to 200 users this way, pick which version each one gets, and revoke access later.
• Share a public link. It gives access to all versions. You can't see who used it, and you can't revoke it once it's shared.

An invite doesn't create a Zap for the user. After accepting, they still have to create a Zap, find your app and turn the Zap on. Ask beta customers early, and give them a specific Zap to build. If you need more Zaps for S002, Zapier suggests creating another Zapier account and inviting it.

Don't delete these Zaps or their runs. Zapier may ask you to share them during review.

3. Set up the test account and team

Two support requirements catch teams on submission day:

• A test account in your app. It must be non-expiring and use the email integration-testing@zapier.com. Zapier support must be able to change the password, unless the account uses passwordless login. Turn on every feature your triggers and actions need, including paid ones, with no trial limits. For complex features, include a demo video or detailed docs.
• An admin with a company email. At least one admin on the integration needs an email address at your app's or API's domain. Zapier's M005 check says the domain must match your homepage URL, and collaborators with that domain don't count.

4. Fill in the listing

These fields become your App Directory listing, and each has a check:

• Name. Your app name exactly as it appears in your branding. Leave out "TM", words like "app" or "integration", and a domain like .ai unless it's part of the brand.
• Description. Start with your app name and "is a", say what the app does, and keep it between 40 and 140 characters (check M002). Don't mention Zapier or other apps, and don't add links. Zapier's example: "Trello is a team collaboration tool to organize anything on a kanban board."
• Logo. A square PNG, at least 256x256 pixels, in RGBA so it can have a transparent background (check M004).
• Category. Required (check M001).
• Homepage URL. Your marketing site, not your login page (checks M006 and 6.3).
• Role. You have to choose employee or contractor of the app's company (check M003).

5. Run validation and submit

All errors and publishing tasks must pass before you can publish. Warnings don't block you, but Zapier recommends reviewing them. Run Run Validation from the Version Overview tab in the Platform UI, or zapier-platform validate in the CLI.

Then submit:

1. Log into the Platform UI and select your integration.
2. In Integration Home, click Publish.
3. Complete the online form.
4. Click Submit for Review.

If a requirement is unclear, Zapier suggests asking its PublishBot first.

6. Review

Zapier says that after you submit, "one of our developers will reach out to you in 1 week or less" with any outstanding requirements. Meanwhile, your version shows as Pending and the integration stays Private.

The one-week promise covers the first contact, not approval. Watch the inbox (and spam folder) of the account that submitted. If Zapier pushes the integration back, make the fixes on a new version and submit that. Check L002 blocks you from resubmitting a version that was already submitted. Don't send repeated submissions of the same integration either. Zapier says that can slow review or bring penalties. If your review goes quiet, see what to do when a Zapier review is stuck.

7. The 90-day beta

When Zapier approves the integration, the status changes to Beta and the integration is added to the App Directory with a Beta tag. It stays in beta for 90 days. Zapier recommends using that time to:

• Publish a help article about the integration on your own site.
• Create Zap templates, which you can do as soon as you're in beta.
• Embed Zapier in your product or website.
• Grow active usage and collect feedback.
• Handle bugs and feature requests with the Zapier Issue Manager.

You can exit beta early. When Zapier detects one Zapier signup from your embed, you leave beta the next business day and unlock Partner Program benefits.

8. Public, and after

After 90 days in beta, the status changes to Public, the Beta tag is removed, and you're added to the Partner Program, with marketing and support benefits.

Listing isn't the end of the work. Once you're public:

• Ship changes as new versions. Zapier's compatibility checks (C001 to C004) compare a new version with the public one and warn about changes that would break existing Zaps, such as removing triggers, input fields or sample data.
• Migrate users off old versions. You can't have more than 100 previous or current production versions with live Zaps (check S003).
• Know the partner contact. If the Zapier team changes your integration, check L004 may block your next changes until you coordinate at partners@zapier.com.

Budgeting the whole program? What a Zapier, Make, n8n or Activepieces integration costs compares agency prices and the time you still spend yourself. Listing on Make too? See how to build a Make custom app from your OpenAPI spec.

Get it built and published under your own accounts

NativeShip turns your OpenAPI spec into official, branded integrations for Zapier, Make, n8n and Activepieces. Your Zapier integration is published from your own Zapier account, with your logo, your company and your support email, and you review each release before anything goes public. Each build is checked with the platform's own tooling, and our team can build, test and submit the integration for review for you. You still bring the test account and the first users. Approval is always Zapier's decision, so we can't guarantee it.

Plans are a one-time $149 (Developer) or $349 (Startup), or we can do it all for you. See pricing.