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.
Updated · platform facts checked against the official docs linked below
At a glance
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
| 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; you can exit early by embedding Zapier in your product.[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
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
- Changelog entryA changelog entry template grouped by Added, Changed, Fixed and Removed, written for users rather than commit logs, with a filled example.
- Onboarding email sequenceA five-email onboarding sequence for new signups: welcome, first win, common blocker, social proof and a check-in, with timing and a filled example.
FAQ
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. Embedding Zapier can end it early.
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 . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch a Slack appSlack app launch guide: Marketplace requirements, 1600×1000 screenshots, privacy and support pages, security rules, and how teams discover Slack apps.
- How to launch a developer APILaunch a developer API: time to first call, docs, OpenAPI, a Postman public workspace, keys and limits, and docs pages that rank.
- How to launch a SaaS productA SaaS launch plan: where buyers find new software, what to prepare, a 4-week timeline, launch-day checklist and the SEO work that keeps signups coming.
- How to launch a WordPress pluginWordPress plugin launch guide: review within 14 business days, readme.txt fields, banner and icon sizes, the no-trialware rule, and SEO.