Launch guidePlugins and integrations

How to launch a Zapier integration

A public Zapier integration puts your product in Zapier's app directory, where people look for tools that connect to what they already use. It comes after your own launch, not before: Zapier's publishing requirements say your app must be fully launched to the public, not in beta or invite-only. Zapier then reviews the integration and lists it with a Beta tag for 90 days while you build docs, Zap templates and usage. Treat those 90 days as the integration's launch. How long the whole thing takes: Zapier gives no build time, because that depends on how many triggers and actions you build. The fixed parts come after you submit: a reply from Zapier within a week, then up to 90 days in beta, which ends the next business day once one person signs up for Zapier through an embed in your product.

Updated September 23, 2026 · platform facts checked against the official docs linked below

At a glance

Building it: Free, in the Platform UI (no code) or the CLI[1]
Review: A Zapier developer replies within a week[1]
After approval: Listed with a Beta tag for 90 days[1]
Exit beta early: One Zapier signup through an embed in your product[1]
Prerequisite: Your app is publicly launched (not beta or invite-only)[2]

Where people find Zapier integrations

Zapier app directory: Users search for the apps they use and browse what connects to them.
Zap templates: Pre-built workflows that show up on both apps' Zapier pages.
Your integrations page: Customers search "{you} + {tool}" before buying.
Your existing customers: The first users of the integration are the people already asking for it.

Assets to prepare

Assets to prepare before launch
Asset	Spec or guidance
Test account	Non-expiring, set up for integration-testing@zapier.com.[2]
Triggers and actions	Built around workflows users actually want, not every API endpoint.[1]
Help docs	How to connect, what each trigger and action does.
Zap templates	Three to five common workflows ready to turn on.
Integration landing page	On your site, with the templates embedded or linked.

Store and listing rules

What the platform itself says, with a link to the page we checked.

After you submit, a Zapier developer replies within a week with any outstanding requirements.[1]
Approved integrations enter a 90-day public beta with a Beta tag. Once Zapier detects one signup through a Zapier embed in your product, the integration exits beta the next business day.[1]
You must work for, be contracted by, or have permission from the company that owns the API; use production endpoints over HTTPS; and never hardcode credentials.[2]
Test every trigger, action and search in live Zaps, provide a non-expiring test account for integration-testing@zapier.com, and name the integration exactly as your brand. Descriptions start "[App name] is a..." and don't mention Zapier.[2]

A 4-week launch timeline

Week 1 · four weeks out
- Make sure the product itself is publicly launched; Zapier won't publish integrations for beta or invite-only apps.
- Ask customers which workflows they'd automate first.
- Build those triggers and actions and test them as a private integration.
Week 2 · three weeks out
- Write help docs.
- Create Zap templates.
- Submit for public review.
Week 3 · two weeks out
- Fix what Zapier's reviewer asks for.
- Build the integration landing page.
- Email customers who asked for Zapier.
Week 4 · launch week
- Announce the Beta listing.
- Track active users of the integration.
- Plan the beta exit (templates, docs, maybe embedding).

Launch-day checklist

Email customers who requested the integration with a template link.
Post the templates on social with a short GIF of a Zap running.
Add the integration page to your site's navigation.

After launch: SEO steps

Launch boards reset; search pages don't. These steps keep people finding you after launch week.

Publish one page per popular pairing ("{you} + {tool}") with a real workflow.
Link Zap templates from your docs.
Update pages when you add triggers or actions.

Common mistakes

Exposing every API endpoint instead of useful workflows.
No Zap templates, so users start from scratch.
Forgetting the 90-day beta is your time to build usage.

Templates for this launch

Where to list it and how to rank it

Where to submit your Zapier integration, and the SEO plan that fits it.

FAQ

How long does it take to build a Zapier integration?

Zapier doesn't publish a build time: it depends on how many triggers and actions you build and how your API handles sign-in. You can build in the Platform UI without code or with the Zapier Platform CLI. After you submit, a Zapier developer replies within a week, and the approved integration spends 90 days in beta unless an embed signup ends it sooner.

How long does Zapier review take?

Zapier says one of its developers will reach out within a week of submission with any outstanding requirements.

What is the Zapier Beta tag?

After approval, integrations are listed with a Beta tag for 90 days while you build docs, templates and usage. Once Zapier detects one signup through a Zapier embed in your product, the integration exits beta the next business day.

Does it cost anything to publish a Zapier integration?

No. Zapier says building a public integration on its Developer Platform is free and there are no publishing fees. Your users pay for their own Zapier plans.

Are Zapier integration pages good for SEO?

Your own "{you} + {tool}" pages can match what buyers search before choosing a product. Give each a real workflow.

Private or public integration?

Build and test privately, then submit public when your triggers and actions cover real workflows.

Sources

Checked September 23, 2026. Platforms change their rules; open the source before you rely on a number.

← All 35 launch guides