What happened to Zapier Functions?
Zapier shut down Zapier Functions. It announced the deprecation on May 29, 2026, stopped anyone creating new Functions from June 1, 2026, and switched off every remaining Function on September 1, 2026. Any Zap step that called a Function has stopped working since then.
Zapier Functions: the shutdown timeline
The primary source is Zapier's help article Important update: Zapier Functions is being deprecated. Zapier says deployed functions "will keep working until the shutdown date", after which "all functions will stop running", and that "your code is preserved" so it can be copied.
Functions were Zapier's way to write and host custom code outside a single Zap and call it from many Zaps. Businesses used them for things like custom data clean-up, price calculations and calls to APIs that have no Zapier integration.
How do you know if a Zap broke?
Open Zap history and filter for errors and halted runs since September 1, 2026. Any Zap that used a Function step will show failures at that step. Also check for Zaps that stopped producing results without an error, such as a CRM that stopped receiving new contacts.
- In Zapier, open Zap history and filter by status: errored or halted.
- Set the date range from September 1, 2026.
- Open each failed run and look at which step failed.
- Check the downstream systems too: new leads in the CRM, rows in the sheet, invoices sent.
The second check matters because a Zap can fail early and send nothing onwards. If lead flow dropped in September and no one knows why, this is worth ruling out first.
What should you replace Functions with?
Zapier recommends Code by Zapier, which runs inside the Zap and supports JavaScript and Python, including npm and PyPI packages. For logic shared by many Zaps, or heavy processing, moving it to a small API or to n8n can be cheaper and easier to maintain.
| Option | Good for | Watch out for |
|---|---|---|
| Code by Zapier | Short logic used in one or a few Zaps | The same code copied into many Zaps drifts apart |
| Built-in Formatter and Paths | Simple text, number and date changes | Gets messy for multi-step logic |
| n8n workflow called by webhook | Shared logic used by many Zaps, heavier processing | A second tool to host and monitor |
| A small custom API | Core business logic, pricing, anything customers see | Needs a developer to maintain |
A good rule: if the same code would be pasted into more than two Zaps, keep it in one place and call it. That is the job Functions did, and a webhook to an n8n workflow or a small API integration does it now.
How do you migrate a Function step by step?
Copy the Function's code, decide where it will live, rebuild the step, test with real sample data from Zap history, then switch the Zap on and watch the first runs. Zapier's migration guide follows the same order.
Migrating a Function step by step
- Copy the code. Zapier says it is preserved even though it no longer runs.
- Note the inputs and outputs. Which fields came in, which fields later steps used.
- Rebuild. Paste into a Code by Zapier step, or move it to n8n or an API.
- Test with real data. Replay a failed run's input from Zap history.
- Re-run what was missed. Where possible, replay the runs that failed since September 1 so no lead or order is lost.
What does this say about building on automation platforms?
Features get retired, even on large platforms, usually with a few months' notice. Keep a simple inventory of which Zaps and workflows depend on which features, and who gets the vendor's deprecation emails. Then a shutdown is a scheduled task instead of a surprise.
This is one reason to write the automation map down at the start of any business process automation project, and one reason our builds come with six months of maintenance. It is also why we avoid putting core business logic in the most proprietary corner of any one tool. If you are choosing between platforms, the Zapier automation page covers where Zapier is the right fit.
Frequently asked questions
When did Zapier Functions stop working?
September 1, 2026. New Functions could not be created from June 1, 2026.
Is my Zapier Functions code lost?
No. Zapier says the code is preserved, so you can copy it and rebuild it in Code by Zapier or elsewhere.
Does Code by Zapier support Python?
Yes. Zapier says Code by Zapier supports both JavaScript and Python, with npm and PyPI packages.
More updates are on the news page. If a Zap broke and you want it fixed, or you want a second opinion on your automation setup, contact us or see our case studies and the automation ROI calculator.
