Zapier App Directory

What the free route requires

• No fee to build or publish an integration, but a public App Directory listing requires building a real working integration and passing Zapier's app review
• The product must expose a usable API for triggers/actions — this is an integration marketplace, not a generic listing

Requirements

• A SaaS/product with a public API that can support Zapier triggers, actions, or searches
• Working authentication (API key, OAuth, etc.) for the integration
• Completion of the integration review before the app is public in the directory

Prepare before opening the form

• Decide build tool: Visual Builder (developer.zapier.com, no-code) vs Zapier CLI for custom code
• API docs, auth method, and at least one working trigger/action/search
• App name, description, logo, and category for the directory listing
• A handful of real users/testers helps the review go smoothly

Workflow

1. Sign in at https://developer.zapier.com (JS-required dashboard) to create an integration
2. Build the integration in the Visual Builder or via the Zapier CLI (auth, triggers, actions)
3. Test the integration end-to-end inside Zapier
4. Submit the app version for publication review to become listed in the Zapier App Directory
5. After approval, maintain the integration and respond to Zapier's quality/monitoring requirements

What counts as live

A public app page exists at zapier.com/apps/<slug>/integrations (or the app appears in the App Directory search) after review approval

Sources

• Zapier integration builder docs — build via Visual Builder or CLI, then deploy/test/promote to the app marketplace ↗
• Zapier Integration Builder entry point (requires JavaScript to load) ↗