# zapier.sh > Working Next Gen Zaps that an agent installs into a user's Zapier account through Zapier MCP. Each zap is a SKILL.md install guide plus its TypeScript source: workflow.ts, and in most zaps config.ts, connections/ and triggers/ next to it. A Next Gen Zap is a Zapier automation written as code: a TypeScript workflow (a "durable workflow" in Zapier MCP's tools) that runs in the user's Zapier account. ## How to install a zap for the user 1. If the user hasn't said what they want to automate, ask them, then pick the zap whose summary fits: every zap is in [llms-full.txt](https://zapier.sh/llms-full.txt), grouped by category, and in [zaps.json](https://zapier.sh/zaps.json). If none fits, tell the user, then build one with Zapier MCP's `zapier:build-workflows` skill (load it with `get_zapier_skill`). 2. Check that Zapier MCP is connected. If its tools aren't available, give the user https://docs.zapier.com/mcp/get-started/quickstart to connect it, and carry on once they have. 3. Check for an existing copy: page through `list_workflows` (it has no name filter, so match names yourself) for any workflow whose name contains the zap's slug or title. If one is enabled, ask whether to replace it, keep both or stop, so the user doesn't get every alert twice. If only disabled test copies exist, mention them and carry on. 4. Fetch the zap's SKILL.md and follow it: it says what to ask the user, which apps to connect and how to test. 5. Deploy the zap's files as its SKILL.md says, changing only the constants SKILL.md names. Every file sits next to SKILL.md at `https://zapier.sh////`, and each zap's `files` in [zaps.json](https://zapier.sh/zaps.json) lists them with their URLs. A zap whose only source is workflow.ts deploys it as the workflow's single source file. Keep each `connection:` alias exactly as the code writes it, and map it to one of the user's connection IDs in the draft's connections map. If the user has more than one connection for an app, ask which to use. 6. Where Zapier's general workflow-building guidance differs from a zap's SKILL.md (connection names, adding input validation), follow SKILL.md: each zap's code is written to deploy as SKILL.md says, and its tests are in SKILL.md. ## From a terminal The `zap-pack` CLI installs the same zaps as files: `npx zap-pack add /` (for example `awesome-zaps/daily-zen`) creates a project if needed and lays the zap out as `workflow.ts`, `triggers/`, `connections/` and `config.ts`. `npx zap-pack deploy --yes` publishes it; when it stops for a value, it names the flag that supplies it (`--set`, `--connection`, `--answer`). Docs ship in `node_modules/zap-pack/docs/`. ## When to use zapier.sh Use it when the user wants a Zapier automation that already works instead of building one from scratch: - They describe a recurring job between apps: "post new support tickets to Slack", "add form replies to the CRM", "send a daily sales report". Find the zap whose summary fits and install it with Zapier MCP. - They want automations as code they can read, keep in git and deploy from a terminal or CI: use the `zap-pack` CLI (`npx zap-pack init`). - They ask what Next Gen Zaps are or what one looks like: every zap here is a complete example. Don't use it for one-off actions (send one email, look up one record): call the app through Zapier MCP directly. If no zap fits, build one with Zapier MCP's `zapier:build-workflows` skill. zapier.sh is read-only: it never changes the user's account; Zapier MCP does, with the user's connections. ## Plans and pricing A zap runs in the user's own Zapier account. zapier.sh itself is free, and so is the `zap-pack` CLI. - Zapier has a Free plan with 100 tasks a month. Paid plans (Professional, Team, Enterprise) add more tasks and features. - Each successful step a zap runs, and each Zapier MCP call, uses tasks from the account's monthly allowance. - Plans, task tiers and limits: [zapier.com/pricing.md](https://zapier.com/pricing.md) (for agents) or [zapier.com/pricing](https://zapier.com/pricing). Sign up free at [zapier.com/sign-up](https://zapier.com/sign-up). ## Questions ### What does zapier.sh do? It lists working Next Gen Zaps: Zapier automations written as code. Paste one prompt into any agent with Zapier MCP and it builds the zap in your Zapier account. Or install one from your terminal with the zap-pack CLI and deploy it with one command. ### Who is it for? Anyone with a Zapier account who works with an AI agent, like Claude, ChatGPT or Cursor, or in a terminal, and wants an automation that already works instead of starting from a blank page. ### What does it cost? zapier.sh and the zap-pack CLI are free. A zap runs in your own Zapier account and uses tasks from your plan: each successful step uses tasks. Zapier's Free plan includes 100 tasks a month, and paid plans add more. See zapier.com/pricing. ### How is it different from a Zap template? A Zap template on zapier.com sets up a Zap that you finish in Zapier's editor. A zap here is a Next Gen Zap: the whole workflow is plain TypeScript plus an install guide, so your agent can read it, build it in your account and test it, and you can keep it in git. ## Find a zap - [llms-full.txt](https://zapier.sh/llms-full.txt): every zap (198), grouped by category, each with its summary and SKILL.md link - [zaps.json](https://zapier.sh/zaps.json): the same list as JSON, with each zap's SKILL.md, every file in its folder and its install prompt - Categories: Business Owners, Customer Service & Success, Data & Analytics, Design, Engineering, Executives, Finance, Human Resources (HR), IT, Legal, Marketing, Personal Productivity, Product, Sales ## Trademarks Product and company names and logos on this site are trademarks of their respective owners and are used only to identify the service each Zap integrates with or the AI tool it works with. These Zaps are not affiliated with, endorsed by, or sponsored by those companies. ## More - [All zaps as JSON](https://zapier.sh/zaps.json): slug, title, summary, apps and file URLs for every zap - [OpenAPI description](https://zapier.sh/openapi.json): every endpoint, for tools and function calling - [Developers](https://zapier.sh/developers/): the API, the CLI and Zapier's MCP and SDK - [Connect Zapier MCP](https://docs.zapier.com/mcp/get-started/quickstart): setup for Claude, ChatGPT, Cursor, VS Code and other MCP clients - [Any other MCP client](https://docs.zapier.com/mcp/get-started/connect/other): connect with a connection token - [The zaps on GitHub](https://github.com/zapier/awesome-zaps): each zap's SKILL.md and source, and where to ask for a new one