Which Zapier OpenAI Assistants Zap Steps Stop on Aug 26, 2026?

If your team runs support triage, document indexing, or data-extraction Zaps through the ChatGPT (OpenAI) app, some of those Zaps now have a hard stop date. Zapier has deprecated every Zap step built on OpenAI's Assistants API, and existing Zaps that use them stop working on August 26, 2026. This post gives you the full affected-step list and three ways to find every affected Zap in your own account.

The full list of Zap steps that stop on August 26, 2026#

The change comes from upstream. OpenAI's Assistants API beta is sunsetting on August 26, 2026, and Zapier has deprecated all ChatGPT (OpenAI) steps built on it. Zapier's deprecation notice puts the consequence plainly:

Existing Zap workflows that use them will continue to run until August 26, 2026, after which they'll stop working.

— Zapier, "Important update: ChatGPT users – OpenAI Assistants API deprecation"

Here is every affected step, exactly as Zapier lists it in that notice. If any Zap in your account uses one of these, it is on the countdown.

Also flag these "(Legacy)" action names while you audit

The ChatGPT (OpenAI) app also carries a set of older actions that gained a "(Legacy)" suffix once the new Responses-API actions shipped. Only Conversation with Assistant (Legacy) appears on the dated list above, but every legacy name is a signal that a Zap is running on an action Zapier has already replaced. Record them in the same audit pass:

• Summarize Text (Legacy)
• Classify Text (Legacy)
• Analyze Text Sentiment (Legacy)
• Analyze Image Content with Vision (Legacy)
• Conversation (Legacy)
• Conversation with Assistant (Legacy)
• Extract Structured Data (Legacy)

Why these Zaps break, and why nothing fixes them for you#

Zapier is not choosing to break your workflows. OpenAI is retiring the Assistants API beta on August 26, 2026, and every ChatGPT (OpenAI) Zap step built on that API goes down with it. Zapier has already hidden the deprecated steps in the Zap editor, so you cannot add them to new Zaps. Existing Zaps keep running only until the date.

This is not an automatic migration. Per Zapier's notice, each affected Zap must be rebuilt by hand on the new Responses-API actions, and after replacing a step you must remap fields in downstream steps, then test and publish. The exact replacement for each deprecated step is covered in the Responses API migration mapping for every deprecated step.

Three ways to inventory your Zaps before the deadline#

You cannot fix what you have not listed. There are three practical ways to enumerate affected Zaps, in order of effort, and all of the essentials work on every Zapier plan.

1. 1

   Start at the App Connection page

   On any plan, open zapier.com/app/assets/connections. Per Zapier's Responses-API article, this page shows all of your Zap workflows that use the ChatGPT (OpenAI) app. That is your candidate list.

2. 2

   Build a simple CSV inventory

   For each candidate Zap, record the Zap name, step number, app, and action name. The load-bearing fields are the app ("ChatGPT (OpenAI)") and the exact action name shown in the step's App & event section.

3. 3

   Or capture a shared-template export

   Sharing a Zap as a template works on all plans and captures the app and event for each step, which is enough to detect affected steps. The full JSON export of Zap workflows is gated to Team and Enterprise accounts, so do not build your audit around it unless you have one.

4. 4

   Match against the deprecated list

   Compare every ChatGPT (OpenAI) action name in your inventory against the table above. Match case-insensitively, and check searches and dropdowns, not just visible action steps.

5. 5

   Assign an owner to every flagged Zap

   A list without owners rots. Give each affected Zap a named owner, a readiness status, and a rebuild date, the same way you would run any vendor API sunset readiness process.

If you would rather not eyeball step names by hand, the free Zapier readiness scan accepts a pasted notice, a CSV inventory, or a shared-template export and flags affected steps without a signup; detection is never paywalled. Duefront's fix-workspace then maps affected Zaps, assigns owners, tracks readiness, and generates evidence packets: stakeholder-ready readiness snapshots, not legal certification.

Worked example: flagging a four-Zap inventory#

Here is a minimal CSV inventory of the kind a small ops team would paste into a checker. Four Zaps, four different outcomes.

zap_name,step_no,app,action
Support triage,2,ChatGPT (OpenAI),Conversation With Assistant (Legacy)
Knowledge base sync,2,ChatGPT (OpenAI),Create Vector Store File
Invoice parser,2,ChatGPT (OpenAI),Extract Structured Data (Legacy)
Lead router,2,Slack,Send Channel Message

Support triage and Knowledge base sync both use steps from the dated list (Conversation With Assistant (Legacy) and Create Vector Store File), so both stop working on August 26, 2026 and must be rebuilt by hand. Invoice parser uses Extract Structured Data (Legacy): a legacy action with a documented Responses-API replacement, but not on the dated Assistants list, so flag it for migration without treating it as deadline work. Lead router never touches the ChatGPT (OpenAI) app and is unaffected.

Common mistakes when auditing for this deadline#

• Waiting for an automatic migration. Zapier's notice describes rebuilding, not converting. Affected Zaps must be rebuilt by hand and downstream fields remapped.
• Matching step names case-sensitively. Zapier's pages themselves differ on "With" vs "with" in the assistant conversation step. A strict string match will miss real Zaps.
• Auditing only visible action steps. Two affected steps are searches and three are dropdowns used inside step setup. A skim of action names misses half the list.
• Treating the AI Actions / NLA wind-down as the same deadline. AI Actions is "no longer being developed and supported" and Zapier points users to Zapier MCP, but there is no published end date. The details are in what the Zapier AI Actions and NLA deprecation actually means.
• Planning around a JSON export you may not have. Zap JSON export is limited to Team and Enterprise accounts. Shared-template exports and the App Connection page work on all plans.