Zapier App Directory

General SaaS

Zapier, Inc. · General SaaS app marketplaces

Best for: SaaS apps wanting broad no-code automation reach with minimal code.

Overview

Zapier is the largest general-SaaS automation directory, with thousands of listed apps consumed by millions of customers. A developer builds one integration — defining triggers, actions, and searches with their auth scheme — via the low-code Platform UI or the Platform CLI, and that single connector becomes usable inside every Zap workflow across the ecosystem. This is classic publish-once, reach-everywhere distribution: the app surfaces in Zapier's directory, in-product search, recommendation emails, and inside other SaaS tools that embed Zapier.

Publishing is free. Zapier reviews each public integration against explicit requirements before it graduates through a 90-day Beta to Public status, after which the partner is auto-enrolled in the Integration Partner Program. Zapier does not take a cut of the partner's revenue and is not a merchant of record — it monetizes its own users on task-based subscription plans. Choose Zapier when the goal is maximum consumer/SMB and prosumer reach with the least engineering lift; its MCP server and Agents product now also make the same connector library callable by AI agents.

How to build & ship

  1. 1Create an integration in the Zapier Platform UI (visual builder) or with the Platform CLI for code-first development
  2. 2Configure authentication (OAuth2, API key, etc.) and test the connection
  3. 3Define triggers, actions, and searches, mapping input/output fields to your API
  4. 4Test each operation in the builder and add sample data
  5. 5Invite users to the private version and reach the required active-user threshold
  6. 6Submit the integration for Zapier's review to move from Beta to Public

Key APIs & SDKs

Zapier Platform UI (visual builder)
Zapier Platform CLI
zapier-platform-core (JS SDK)
Triggers / Actions / Searches model
Authentication schemes (OAuth2, API key)

Integration types

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key, JWT
  • Security review: Required
  • Zapier reviews every public integration against published requirements before it moves Pending → Beta (90 days) → Public.
  • Zapier runs a design/functionality review before an integration goes Public, and it must first meet an active-user requirement in Beta; review commonly takes about one to two weeks.
  • Varies by plan and by the partner's own API; Zapier throttles polling and task volume per account tier.

Monetization

Onboarding
$0 (free to list)
Commission
None (no partner rev-share; Zapier monetizes end-user task volume)
Merchant of Record
Not applicable (partners bill their own SaaS separately)

Pros & cons for builders

Pros

  • Largest no-code automation audience with thousands of connected apps
  • Choice of visual builder or code-first CLI
  • Strong docs, samples, and a well-defined trigger/action model
  • Public listing drives meaningful inbound discovery

Cons

  • Public listing gated by an active-user threshold and a design review
  • Polling-based triggers and platform constraints limit some advanced logic
  • Ongoing maintenance expected to keep the listing published