All of Zapier's code capabilities, in one place.
Code by Zapier is the unified home for code at Zapier: JavaScript and Python steps, npm packages, AI-assisted code generation, and the Zapier SDK, all with extended runtimes, inside the Zaps you already trust.
A note for Functions beta users: Thank you for being part of the Functions beta. What we learned from your usage directly shaped Code by Zapier — the consolidated home for code on our platform. Functions is winding down on September 1, 2026, with migration support along the way. Read the migration guide →
Write JavaScript or Python, right inside any Zap
Drop a code step into any Zap to transform data, call any API, or run logic that's hard to express in pre-built actions. Same Zap history, same retries, same governance you get from any other step, plus extended runtimes, AI-assisted code generation, and a deep editor experience.
Use the npm ecosystem
Pull in the npm packages you already know — zod for validation, date-fns for time math, your favorite parsing libraries — straight from the editor. No transpiled bundles, no workarounds.
Generate code with AI
Describe what you want in plain English and let AI write the JavaScript or Python for you, right inside the Zap editor. Iterate, edit, and ship without leaving the canvas.
Orchestrate across 9,000+ apps
The Zapier SDK is now available inside Code by Zapier code steps. With one import, your code can run any Zapier app action and orchestrate multi-app logic across 9,000+ supported apps, all from a single code step. And when you need to reach an app Zapier doesn't support yet, use the SDK's authenticated fetch to call its API directly, with Zapier injecting the credentials for your connected account.
Run code outside Zapier with the standalone SDK
Building scripts, internal tools, or coding-agent workflows? The Zapier SDK is also available in open beta as a standalone TypeScript SDK. It has the same managed authentication, same access to 9,000+ apps, but running wherever your code runs (Cursor, Claude Code, Railway, your laptop). That means workflows that start as a code step in a Zap can grow into standalone services without rewriting auth or integration logic.
Working with a coding agent? There's a Zapier SDK skill that teaches your agent how to use it. Run the quick-start prompt and your agent installs it automatically, or add it yourself with npx skills add zapier/sdk -y
FAQ
What's happening to Zapier Functions?
Zapier Functions is winding down on September 1, 2026. We're consolidating all our code investment into Code by Zapier — which now includes the Zapier SDK, npm packages, and AI-assisted code generation, with run times up to ten minutes and more on the roadmap. Read the migration guide →
I have a Function in production today. What do I need to do?
Through September 1, 2026, your existing Functions continue to run as normal. New builds should happen in Code by Zapier. Enterprise customers will hear from their TAM/CSM directly with a migration plan. Self-serve customers can [contact support] or check the migration guide for guidance on how to move your code.
Will my Functions automatically migrate to Code by Zapier?
No. To make the move as easy as possible, we're providing a migration guide, common-pattern recipes, and an LLM-assisted migration tool. For complex cases, our support team is here to help.
What is the Zapier SDK?
The Zapier SDK is a TypeScript library that lets your code call any of Zapier's 9,000+ integrations using the connections you've already authorized — no hardcoded API keys, no OAuth setup, no private integration to build. It's available in two places:
- Inside Code by Zapier code steps, so you can orchestrate multi-app logic from a single step in any Zap.
- As a standalone SDK in open beta, so you can run code outside Zapier (in Cursor, Claude Code, Railway, your own backend) with the same managed auth.
Do I have to learn JavaScript to use Code by Zapier?
No — Code by Zapier supports both JavaScript and Python today. The Zapier SDK is currently JavaScript-first.
What about features I used in Functions — multi-trigger, secrets, multi-file?
These are known gaps we're actively closing in Code by Zapier. In the meantime: multi-trigger has a Sub-Zap workaround; secrets are addressed for many use cases by API by Zapier today, with masked variables coming; multi-file support is on the roadmap. Full details in the migration guide.
Where do I learn more?
Start with the Code by Zapier guide. For the SDK, see docs.zapier.com/sdk. The Zapier Community is a great place to get help from other code-first users.