---
name: zapier-integrations-guide
description: >
  Use when asking which Zapier integration developer tool to use, "Platform UI versus Platform CLI",
  integration structure, private versus public integrations, publishing requirements, or beta status.
  Explains the integration developer tools and routes to canonical documentation.
license: MIT
compatibility: >
  Applies to docs.zapier.com public documentation.
metadata:
  author: zapier
---

# Zapier integrations guide

A Zapier integration defines an app's authentication, triggers, and actions so people can use that app in Zapier. Developers build integrations with the Platform UI (a browser-based visual editor) or the Platform CLI (JavaScript in a local development environment).

## Critical rules

- **The app needs a publicly accessible API.**
- **OAuth v1 needs the Platform CLI.** The Platform UI does not support OAuth v1 for new integrations.
- **Platform CLI only:** custom middleware, file support, hydration, NPM modules, and custom automated tests.
- **Platform UI to Platform CLI:** export the integration. The reverse has no direct export.
- **All integrations start private.** An approved public integration is in beta for 90 days with a Beta tag in the app directory.
- **Publishing requirements apply** before an integration can go public.

## Platform UI or Platform CLI

| If you need... | Use |
|---|---|
| A form-based editor, with Code mode for some advanced calls | Platform UI |
| Local development, version control, or custom automated tests | Platform CLI |
| OAuth v1 authentication | Platform CLI |
| JavaScript control over request handling | Either |

Zapier advises the Platform UI when the comparison does not settle it.

## Canonical documentation

- [Integration quickstart](https://docs.zapier.com/integrations/quickstart/build-integration): start here
- [Platform UI and Platform CLI comparison](https://docs.zapier.com/integrations/quickstart/ui-vs-cli): full feature table
- [Integration structure](https://docs.zapier.com/integrations/quickstart/zapier-integration-structure): parts of an integration
- [Private versus public integrations](https://docs.zapier.com/integrations/quickstart/private-vs-public-integrations): audience and limitations
- [Publishing requirements](https://docs.zapier.com/integrations/publish/integration-publishing-requirements): what a public integration must meet
- [Operating constraints](https://docs.zapier.com/integrations/build/operating-constraints): time and payload limits

## Related skills

- `zapier-mcp-guide`: using existing Zapier actions from an AI client
- `zapier-sdk-guide`: using existing Zapier actions from code
- `zapier-troubleshooting-router`: errors while you build