Zapier Functions shuts down tomorrow: migrate now

Zapier Functions shuts down tomorrow, September 1, 2026. Every function still running there stops executing, and the interface that runs them disappears with it.

Functions was Zapier's standalone code tool, small Python snippets you could write once and call from anywhere in your account, not tied to a single Zap. New signups stopped back on June 1. Now the whole thing goes dark, and Zapier is folding those capabilities into Code by Zapier, the code step that already lives inside your Zap workflows.

Why Zapier Functions is being retired

Zapier ended up running two code tools that did overlapping jobs. Code by Zapier now supports JavaScript and Python natively, pulls in npm and PyPI packages, and includes AI assisted code generation and the Zapier SDK. Once the newer tool covered everything the older one did, keeping both around stopped making sense, so the smaller one closes.

What breaks if you use Functions

If a Zap calls a function you built, that step stops returning results the moment the shutdown lands. The Zap does not pause gracefully, it fails at that step, and anything downstream of it, an email, an invoice update, a CRM record, never fires. If you have never opened the Functions tool in your Zapier account, none of this touches you.

1. 1

   Copy your code now

   Open each function from the Functions home and save the Python source somewhere outside Zapier. The interface disappears at shutdown, code and all, so do this today rather than tomorrow morning.

2. 2

   Build one Zap per trigger

   Functions could hang off multiple triggers at once. Code by Zapier ties a code step to a single Zap, so a function with three triggers becomes three separate Zaps.

3. 3

   Add a Code by Zapier step

   Pick JavaScript if the function called the Zapier SDK or an outside API, Python if the logic was self contained. Python syntax mostly carries over, but variable handling differs enough to need a real pass, not a copy and paste.

4. 4

   Move secrets out of the code

   Code by Zapier will not store API keys inside the code step itself. Route authenticated calls through API by Zapier and the Zapier SDK instead of a bare fetch call with a key hardcoded in.

5. 5

   Test before you publish

   Run the new step against real data and check every downstream field mapping. A step that fails loudly is an inconvenience. A step that quietly returns the wrong value is the one that costs you a client.

If you never touched Functions

This one event is small. The pattern behind it is not. Automation vendors regularly retire a free or lightweight tool and fold it into a paid, more capable replacement, on a timeline set by them, not by your calendar. The useful habit isn't watching Zapier specifically, it's knowing which of your automations lean on a feature narrow enough to get consolidated away with three months notice.

If part of your stack still runs on Zapier Functions, get the code copied out today, not after the interface is gone. And if you want someone to walk your automations and flag what else is quietly resting on a feature a vendor could retire next, that's a conversation worth having.