Builder · Level 2 of 3
Zapier Functions stopped running on September 1, 2026. Code by Zapier is the documented migration path for custom JavaScript or Python inside Zaps. Inventory every caller, recover the source code, then test inputs, outputs and connected actions before replacing the old call. This guide uses an illustrative data transform; it does not claim an AML production migration or a measured completion time.
Some links below are affiliate links. If you sign up through them, Automate My Life may earn a commission at no extra cost to you, which helps keep the site free. Only genuinely useful tools receive a recommendation.
What Changed When Zapier Retired Functions
Zapier folded its standalone custom-code tool, Zapier Functions, into Code by Zapier, the code step already available inside the normal Zap editor. Code by Zapier runs natively in a Zap workflow rather than as a separate tool with its own dashboard, and it supports both JavaScript and Python, npm and PyPI packages on paid plans, AI-assisted code generation, and the Zapier SDK for calling connected apps from code (JavaScript only).
| Date | What happened |
|---|---|
| June 1, 2026 | Functions stopped accepting new users. |
| September 1, 2026 | All functions stopped running. The Functions interface is no longer accessible, though Zapier says the code itself was preserved rather than deleted. |
Zapier says it preserved Function code during 2026, but the old interface is inaccessible. Start with your own repository or export and follow Zapier’s migration guidance or support route if the source is missing. A run’s output or logs are not a reliable copy of the original program. Do not paste credentials or customer records into a recovery request.
These shutdown dates come directly from Zapier’s own Functions deprecation announcement, last updated May 29, 2026.
Is One of Your Zaps Actually Affected?
You are affected if any Zap includes a step that calls a Function specifically, not a Code by Zapier step, which is a different, unaffected step type living in the same editor. Since September 1, any Zap still pointed at a Function has been erroring every time it tries to run that step, so a Zap that quietly stopped working around then is the clearest sign.
- Open each active Zap and check its step list for a step labeled “Function” (the older naming) rather than “Code by Zapier.”
- Check the Zap’s run history for errors dated on or after September 1, 2026 that reference a function call.
- Note which app and trigger each affected Zap uses before you start rebuilding, so you can recreate the same trigger in the new Zap.
- If a function was called from more than one Zap, list all of them now. Each one needs its own migration.
Step-by-Step: Migrating a Function’s Code into Code by Zapier
Work in a disabled draft or copy of the affected Zap. Follow the current migration guide to replace the Function call with a Code action and reconnect its inputs and outputs. The example below shows a small transform in two languages; it is illustrative, not a previously tested customer migration.
- Record the trigger, connected account and downstream actions, then edit a disabled draft or controlled copy. Keep the original definition available for comparison and rollback.
- Add a Code by Zapier step as the action, and choose “Run JavaScript” or “Run Python.” Pick JavaScript if the function called another app’s action directly, since that needs the Zapier SDK, covered below. Otherwise Python is usually the smaller edit if the function was already written in Python.
- Paste the old function’s code in and adapt it to the new step’s input and output format. The variable names change even when the logic doesn’t.
| In a Function | In Code by Zapier |
|---|---|
| input_data[‘key’] | inputData.key |
| output = {‘key’: ‘value’} | output = { key: ‘value’ } |
| print(value) | console.log(value) |
| Python’s requests library | fetch() in JavaScript, or Python’s own HTTP calls in a Python step |
For a harmless first check, map a sample summary string into a Python Code action and trim surrounding spaces. This avoids sending messages or making API writes while you learn the input and output mapping. The Python form is:
summary = str(input_data.get("summary", "")).strip()
output = {"summary": summary}
The same logic in a JavaScript Code by Zapier step:
const summary = String(inputData.summary ?? "").trim();
output = { summary };
Keep secrets out of Input Data, source code and logs. For authenticated actions, use an existing app connection through the Zapier SDK, or an API by Zapier connection where appropriate. Zapier documents those connection-based paths for protected credentials. The transform above deliberately needs no token or network call. Preserve Python when it fits; the comparison table illustrates syntax differences, not a required language conversion.
- If the function called another Zapier-connected app directly (the zapier.action pattern), rewrite that call using the Zapier SDK in a JavaScript step. The SDK is JavaScript-only, so this is the one migration path with no Python option.
- Test the step inside the Zap editor before publishing, and re-map any downstream fields. Code by Zapier’s output does not always match the old function’s output field for field, so a later step that referenced the function’s output may need to point at a new field name.
- Before cutover, test with dummy records and controlled destinations. Stop the original workflow at a recorded event boundary, reconcile in-flight work, then enable the replacement. Keep a rollback copy; do not let both versions send real messages or perform the same production write.
What Is Actually Different in Code by Zapier
A few practical differences show up once you are working inside Code by Zapier day to day, rather than in the old, separate Functions tool:
- Two languages in one place. JavaScript and Python both run as Code by Zapier steps, instead of picking a language once per function.
- Packages need a paid plan. npm and PyPI package support ships on Zapier’s paid plans, not the free plan.
- Runtime limits scale with your plan. Free-plan code steps get one second of standard runtime and no extended-runtime option. Paid plans get meaningfully longer runs: Professional and Team get 30 seconds of standard runtime, Enterprise gets 2 minutes, and Professional, Team, and Enterprise can extend a step up to ten minutes with extended runtimes rolling out through 2026.
- Rate limits are generous on paid tiers. Professional and Team plans can run 225 calls every 10 seconds through a Code by Zapier step, the same ceiling Enterprise gets, well above what most single-function migrations will ever need.
- There is a combined size limit. Code by Zapier steps run in a hosted environment with a 6 MB ceiling across your code and the data it processes in one run, worth knowing if a function used to handle larger files or payloads.
- AI-assisted code generation is still there. It is built into the same editor Functions used to call Copilot, so the assisted-coding workflow did not go away, it was renamed and relocated.
- Shared callers need an inventory. A Zap may contain multiple Code steps. If several workflows called one Function, account for every caller and decide where shared logic belongs; migration is incomplete while a caller still points at the retired service.
Runtime, rate-limit, and size-ceiling figures above come from Zapier’s own Code by Zapier documentation, rate-limit reference, and JavaScript code step guide, reopened October 30, 2026.
When to Consider Make or n8n Instead
For a straightforward Function, migrating in place is the right call, and nothing here is a reason to rebuild a whole automation on a different platform. But a small number of cases are genuinely better served by Make or n8n than by writing more code inside Zapier, and it’s worth naming them honestly rather than treating Code by Zapier as a universal fit.
- Branching workflow logic. Make can be worth comparing when a visual workflow is easier for you to maintain. Model its actual credit usage and required connections rather than assuming a code migration requires changing platforms. Check Make’s current plan options.
- You need control over hosting. Consider a self-hosted workflow tool only if you can maintain its server, updates, credentials and backups. Verify the current license and required features. Self-hosting does not remove infrastructure costs, capacity limits or third-party API restrictions. Review n8n’s current options.
- The Zap was already fighting the platform. If a Function existed because Zapier’s trigger-and-action model kept getting in the way of what you were building, that’s a signal about the platform, not just the code step. The fuller Zapier vs. Make vs. n8n comparison is worth reading before you invest more time patching around it.
Switching platforms is a bigger project than moving one code step, so it isn’t worth taking on lightly just because a deprecation forced your hand this once.
Common Migration Pitfalls (and How to Avoid Breaking the Zap)
- Pasting Python requests code into a JavaScript step. The two languages aren’t interchangeable line for line; use the mapping table above rather than copying across languages.
- Leaving a secret in plain text inside the code. Since Code by Zapier can’t store secrets the way Functions could, route anything sensitive through API by Zapier and the Zapier SDK, or a connected account, instead of hardcoding it.
- Not re-mapping downstream fields. A later step that reads the function’s old output field will silently break if Code by Zapier’s output uses a different key, so check every downstream step, not just the code step itself.
- Migrating only one Zap when a function served several. Track down every Zap that called the function before you consider the migration finished, since each one needs its own Code by Zapier step.
- Skipping the test run before publishing. Publish a migrated Zap only after a successful test, the same as you would for any new automation.
Costs and Plan-Limit Differences Worth Knowing
Check your current entitlement before choosing the replacement design. Packages, longer runtime, authenticated connections and downstream apps can have plan requirements. A code-only transform and a connected multi-app workflow do not necessarily need the same features or budget.
| Platform | What to price | What it gets you for code |
|---|---|---|
| Zapier | Required plan, billable tasks and any extended-runtime usage | Code by Zapier ships on every plan, but npm/PyPI packages and extended runtimes need a paid plan. |
| Make | Required plan, actual credits, retries and connected services | Visual modules can replace some custom code; billed on credits, not tasks. |
| n8n | License rights, server, backups, maintenance and connected services | Self-hosting shifts operational duties to you; verify feature and license requirements. |
Desk review, October 30, 2026: the linked Zapier deprecation, migration, Code, JavaScript and rate-limit documentation supports the migration path and plan-dependent constraints. The code snippets are illustrative and have not been run in an AML Zapier account. No paid-plan price or savings benchmark is asserted here; check the actual plan, execution usage and required connection rights before committing.
Wrapping Up
If you just needed to get an existing Function working again inside Code by Zapier, the steps above cover it end to end. If this deprecation has you reconsidering the whole platform rather than one code step, Zapier vs. Make vs. n8n in 2026 lays out the fuller comparison, and the roundup of Zapier alternatives is worth a look before you commit to a rebuild.
Desk-researched guidance; no AML hands-on run, account benchmark, or guaranteed outcome is claimed.