Disclosure: Some links on this page are affiliate links. If you buy through them, StackPilot may earn a commission at no extra cost to you. Learn more.
OpenAI is retiring the Assistants API, and Zapier has deprecated every ChatGPT action built on it. On August 26, 2026, Zaps still using those actions stop running. Some get migrated automatically — but they're left switched off. Here's the two-minute audit worth doing before the deadline.
OpenAI announced it is deprecating the Assistants API — the interface that let developers and automation platforms create persistent AI "assistants" with instructions, memory, and file access — in favor of its newer Responses API. Zapier, which built several of its ChatGPT (OpenAI) integration actions on top of Assistants, has deprecated all of them and set a hard cutoff: existing Zaps using these actions run until August 26, 2026, then stop.
The deprecated pieces, per Zapier's help center: the actions Conversation With Assistant (Legacy), Create Assistant, and Upload File (when used with assistants); the searches Find Assistant and Find or Create Assistant; and the dropdowns List Assistants and List Assistant Files. They're already hidden in the Zap editor, so you can't add them to new Zaps — the deadline only matters for automations you built in the past and may have forgotten about.
Zapier is handling the most common case automatically. Zaps using Conversation With Assistant (Legacy) get migrated to the new Conversation action, which runs on the Responses API and supports memory, file search, web search, and MCP tool calls.
The catch: migrated Zaps are left turned off. Zapier wants you to confirm the configuration and remap any fields used in later steps before re-enabling. If you have a lead-qualification or support-triage Zap running through an assistant and you don't turn the migrated version back on, that workflow silently goes dark on the 26th — no error email from a Zap that isn't running.
Everything else — Create Assistant, Upload File, Find Assistant, Find or Create Assistant — has no direct replacement. Those workflows need to be rebuilt with current ChatGPT actions or redesigned entirely.
Because OpenAI is retiring the API itself, this reaches beyond Zapier. If you run Make scenarios, custom scripts, or any third-party tool that calls the Assistants API directly, those break on OpenAI's shutdown timeline regardless of platform. Microsoft has fielded the same questions about Azure OpenAI's Assistants support. Wherever an "assistant" object lives in your stack, it's worth checking now.
This is the second time in a year that Zapier users have had to react to an upstream AI platform change, and it won't be the last — AI vendors are consolidating APIs fast, and automation platforms inherit every one of those changes. Two practical takeaways: keep an inventory of which automations depend on which AI provider, and prefer platform-native actions (like Zapier's Conversation) over legacy or beta integrations when both exist — the native ones get migration support; the legacy ones get deadlines.
If you're comparing automation platforms on how they handle exactly this kind of churn, our Make vs Zapier comparison covers the tradeoffs in depth.
The AI & Automation Stack Playbook covers how to pick tools, wire them together, and avoid single points of failure — for $29.
Get the Playbook →