Zapier shuts down Zapier Functions and moves code to Code by Zapier

Zapier shut down Zapier Functions, one of its products for running code, on September 1, 2026. Zapier’s help article on the change was first published on April 20, 2026. Zapier stopped new sign-ups and new functions on June 1 and kept existing functions running until the shutdown date.

What changed

After September 1, all functions stopped running. Deployed functions no longer execute, and the Functions interface can no longer be opened. Zapier says it is folding its code features into one product, Code by Zapier, which runs inside Zap workflows.

Date	What happened
April 20, 2026	Zapier publishes the deprecation notice
June 1, 2026	No new sign-ups or new functions
September 1, 2026	All functions stop; the interface closes

What you keep

Zapier says your code is preserved and that no code will be deleted in 2026. The help article told users to open each function and copy its code before the shutdown. It does not say how to get at the code after September 1, so contact Zapier Support if you missed the deadline.

The replacement

Code by Zapier runs as a step inside a Zap and supports both JavaScript and Python. It can use npm and PyPI packages and offers AI-assisted code generation. To call app actions from code, Zapier points to the Zapier SDK, which works only with JavaScript. Zapier publishes a step-by-step migration guide from Functions to Code by Zapier.

Zapier’s help center has a separate article on how Code by Zapier usage is measured. Read it before you move busy workflows, so the rebuilt steps don’t surprise you on your plan’s usage.

Who is affected

Anyone who built workflows on Zapier Functions. Zapier pointed Early Access Program users to its EAP Slack for questions and everyone else to Zapier Support. Zapier users who never used Functions are not affected.

What to do

If a workflow stopped on September 1, rebuild the function as a Code by Zapier step, test the Zap, then publish it. For Python code that called app actions, plan to rewrite that part in JavaScript or use regular Zap action steps instead.