Zapier SDK skill
Plugin with the zapier-sdk skill: an agent writes code for 9,000+ Zapier apps and takes action keys from the live catalog
- 269 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Through the connected OAuth grants an agent can write to Gmail, Slack, CRMs and other apps as the account owner
- zapier.fetch sends an HTTP request to any address with the chosen connection's authorisation
- The clientId and clientSecret credentials sign in to the SDK without a browser
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/zapier-sdkDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Through the connected OAuth grants an agent can write to Gmail, Slack, CRMs and other apps as the account owner
- zapier.fetch sends an HTTP request to any address with the chosen connection's authorisation
- The clientId and clientSecret credentials sign in to the SDK without a browser
This is third-party code. Review the repository files before installing.
What it does
The zapier/sdk repository is an official bundle for Claude Code, Codex and GitHub Copilot CLI that teaches an agent to work with the Zapier SDK for TypeScript. It has three parts: the zapier-sdk skill, the zapier-sdk-explorer subagent and a corpus of verified examples. The skill covers logging in, finding an app and an action in the Zapier catalog and running the action on the user's behalf. The skill's main rule is that a model's memory of this SDK is outdated and cannot be trusted. The agent first looks up the app key with zapier-sdk list-apps, then the action with list-actions and the input fields with list-action-input-fields, and only then writes code. The zapier-sdk-explorer subagent is read-only: it checks identifiers against the live catalog and runs or deploys nothing. Examples are organised by app, by domain and by pattern: event notifications, data sync, lead routing, scheduled reports. When the catalog lacks an action, the skill points to zapier.fetch, a plain HTTP request authorised through a Zapier connection. A separate reference covers durable workflows that run on Zapier's infrastructure.
Who it is for. Developers who build a TypeScript backend or agent with actions in Gmail, Notion, Google Sheets or HubSpot and do not want to maintain OAuth for each app separately.
Good fit when
- A Node script must find a row in Google Sheets and send an email through Gmail, and you do not want to manage each service's tokens
- An agent in Claude Code invents Zapier action keys, and you need a subagent that checks them against the live catalog
- Facebook Lead Ads leads must be routed to HubSpot or Google Sheets, and the corpus already holds examples of that routing
- A daily revenue summary must go out on a schedule: the examples catalog holds a sample of such a report
Not a fit when
- You want to call apps straight from Claude Desktop or ChatGPT with no code: Zapier has a separate MCP server for that
- Company policy forbids handing OAuth grants to an intermediary: Zapier holds the app connections
- The script must run in an isolated network with no outbound access: the SDK talks to the Zapier platform over HTTPS
Example request
Write a TypeScript script that uses the Zapier SDK to find Notion pages titled "Meeting Notes" and print themLimitations
- A Zapier account is required: npx zapier-sdk login opens a browser, and terms and pricing are on zapier.com/sdk.
- A person approves access to each app through OAuth. The agent can fetch the link and show it but cannot press "allow" for you.
- Actions marked is_hidden sit outside the stable surface: Zapier does not promise they will keep working.
- Third-party rate limits reach your code as a ZAPIER_ACTION_ERROR with a retry delay in seconds, and you write the retries and queues.
How to disable. Turn the plugin off in the /plugin menu of Claude Code, or with the toggle in /plugins in Codex. npm uninstall @zapier/zapier-sdk removes the package from a project. npx zapier-sdk list-connections shows the connections Zapier holds.
FAQ
How do I install the Zapier SDK in Claude Code?
Two commands in Claude Code: /plugin marketplace add zapier/marketplace and /plugin install sdk@zapier. The plugin brings the skill and the subagent, while the SDK itself goes into the project separately with npm install @zapier/zapier-sdk. Codex and Copilot CLI use the same shape: codex plugin add sdk@zapier and copilot plugin install sdk@zapier.
What if there is no connection to the app yet?
Create one with npx zapier-sdk create-connection notion, replacing notion with the app you need: a browser opens for OAuth. Following the skill, the agent fetches the link with get-connection-start-url, shows it to you and waits with wait-for-new-connection.
How do I run the code on a server or in CI with no browser?
Pass client credentials to createZapierSdk: credentials with clientId and clientSecret fields. Browser login is only for local development.
Does the skill work with Cursor?
Yes, without the plugin. The skill follows agentskills.io, so after git clone https://github.com/zapier/sdk.git you reference skills/zapier-sdk/SKILL.md from .cursorrules or AGENTS.md.
Can I call an API that is not among Zapier's actions?
Yes, through zapier.fetch: it sends an HTTP request with the chosen connection's authorisation and lands in the same audit trail as runAction.
Discussion
No questions or reviews yet.
Related
SkillsZapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
The Vercel chat-sdk skill: the agent writes Slack, Teams, Discord and Telegram bots from one codebase and picks the adapters.
Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
A skill that equips an agent with Kody CLI for local code execution using shared memory, packages and cloud account data.
Skills for HR and recruiters: role requirements, sourcing on BOSS Zhipin and Liepin, resume review, interviews and a candidate ledger
AI Agent Skills by sanjay3290
AI Agent Skills
Cross-platform agent skills: read-only PostgreSQL, MySQL and MSSQL queries, Google Workspace, Jira, Telegram, text-to-speech and research
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Zapier SDK (this card) | yes | 269 | ||
| Zapier MCP | yes | OAuth | 453 | the same Zapier, but calls run as MCP tools in chat with no code written |
| Composio | no | 30,937 | a third-party integration platform with its own SDK, CLI and MCP rather than the Zapier catalog |
README in short
The README opens with a quick start: two npm packages, login, creating a connection and running an action through the CLI. Next come the example catalog in three cuts, a diagram of how code reaches the Zapier platform and ways to install the plugin in different assistants. The service's own terms are left to the Zapier Terms of Service.
README badge
Original SKILL.md
--- name: zapier-sdk description: | Zapier SDK for TypeScript. Programmatic access to 9,000+ apps on a user's behalf via Zapier's OAuth and audit layer. Use when writing code that needs to run actions in third-party apps (send an email, upsert a CRM record, look up a spreadsheet row, post to a chat) without managing per-app OAuth or vendor SDKs. Triggers: "zapier sdk", "zapier-sdk", "@zapier/zapier-sdk", "runAction", "run zapier action", "connect to app via zapier", "zapier connection", "zapier tables", "list actions for zapier app", "getActionInputFieldsSchema", "createZapierSdk". metadata: author: zapier --- # Zapier SDK Connect your app, agent, or backend to 9,000+ integrations with a few lines of code. Run actions, manage user connections, chain apps together. The SDK handles token refresh, retries, and API differences. ## When to use the SDK The Zapier SDK is the **code interface** to Zapier. It gives coding agents and AI builders programmatic, governed access to 9,000+ apps, running inside editors like Cursor, Claude Code, or VS Code. Two sibling interfaces share the same capabilities: - **Zapier CLI** (`@zapier/zapier-sdk-cli` package): terminal interface (`npx zapier-sdk ...`) for one-off commands, exploration, scripting. Read [`references/cli.md`](references/cli.md) when the user wants shell access instead of code. - **Zapier MCP** (https://zapier.com/mcp): LLM interface (tool-calling inside Claude, ChatGPT, or any MCP client, no code required). Pick the SDK when the deliverable is code. If the user wants ad-hoc tool calls in an AI chat interface, point them to MCP. **Two SDK shapes to distinguish:** - **Plain SDK script** (this file): the user's own code calls the SDK. Runs wherever their code runs (Node script, Next.js route, Lambda, CLI). - **Durable workflow** (`@zapier/zapier-durable`): the user *deploys* a workflow that Zapier's infrastructure runs on a trigger (webhook, poll, schedule). Retries stay idempotent via `ctx.step`. Read [`references/workflows.md`](references/workflows.md) when the user wants deployment on Zapier's infrastructure instead of running the code themselves. ## Prerequisites The SDK ships two packages: a TypeScript library and a CLI. Install whichever you need. Check what's already installed: ```bash # Is the SDK library present? ls node_modules/@zapier/zapier-sdk 2>/dev/null && echo "SDK installed" || echo "SDK not installed" # Is the CLI available? npx zapier-sdk --version 2>/dev/null && echo "CLI installed" || echo "CLI not installed"