Migrating Zapier Assistants Steps to Responses API: Full Mapping

Your Zaps still run today, but every ChatGPT (OpenAI) step built on the OpenAI Assistants API stops working on August 26, 2026. If you own one of those Zaps, you need two things: the exact from-to replacement mapping, and the rebuild procedure. Zapier migrates none of it for you.

The complete from-to replacement mapping#

The mapping below comes from Zapier's deprecation notice for the OpenAI Assistants API steps. Five legacy step families have a named Responses-API target. The Assistants-specific steps do not, and they get their own section further down.

When a legacy conversation step was doing simple, stateless work, you have a second option besides Conversation. Zapier's guidance in the deprecation notice is direct:

Use Conversation for back-and-forth conversations with memory, file search, web search, and MCP tool support. Use Send Prompt for simple, one-off prompts that do not need memory.

— Zapier, OpenAI Assistants API deprecation notice

Why the step names changed underneath you#

The trigger is upstream: OpenAI is deprecating the Assistants API, and Zapier has deprecated every ChatGPT (OpenAI) step built on it. Zapier's notice is blunt: "Existing Zap workflows that use them will continue to run until August 26, 2026, after which they'll stop working." The deprecated steps are already hidden in the Zap editor and unavailable for new Zaps.

On the replacement side, the ChatGPT (OpenAI) app now exposes four actions built on the Responses API: Conversation, Analyze Text, Analyze Images, and Extract Structured Data. That is why the mapping is many-to-one. For the full timeline and affected-step list, see why Zapier's OpenAI Assistants steps stop on August 26, 2026.

One scoping note: this post covers only the dated track. The separate AI Actions and NLA wind-down has no published date. Zapier describes AI Actions as no longer being developed and supported, and points users to Zapier MCP instead.

The rebuild procedure, step by step#

1. 1

   Inventory every Zap that touches ChatGPT (OpenAI)

   Zapier's own audit path is the App Connection page, which lists every Zap workflow using the ChatGPT (OpenAI) app. On Team and Enterprise plans you can also export your Zap workflows as JSON from Settings, under Security and data.

2. 2

   Match each step name against the mapping table

   The load-bearing fields are the app plus the action name shown in the step's App & event section. Match case-insensitively: Zapier's own pages alternate between "Conversation With Assistant (Legacy)" and "Conversation with Assistant (Legacy)".

3. 3

   Replace the step with its Responses-API action

   Swap the legacy conversation steps for Conversation, the three legacy text steps for Analyze Text, the vision step for Analyze Images, and Extract Structured Data (Legacy) for its Responses-API version. Use Send Prompt instead when the step is a simple one-off prompt with no memory.

4. 4

   Remap fields in every downstream step

   Replacing a step changes its output fields, so each downstream step that referenced the old step must be re-pointed at the new fields. Zapier's notice calls this out explicitly: after replacement, you remap fields in downstream steps.

5. 5

   Test the Zap, then publish

   Run a test on the rebuilt step, confirm downstream steps receive what they expect, and publish. If you are doing this across a team, track each Zap's state with a repeatable vendor sunset readiness process instead of a group chat.

A worked example: swapping a legacy text step#

Here is the shape of the swap for a common pattern: a Zap that summarizes inbound support tickets. The action name changes in one step; the real work is the downstream remap and retest.

Before (stops working Aug 26, 2026)
  App:    ChatGPT (OpenAI)
  Action: Summarize Text (Legacy)
 
After (Responses API)
  App:    ChatGPT (OpenAI)
  Action: Analyze Text
  Then:   remap output fields in every downstream step,
          test the Zap, and publish

Finding affected steps in a Zap export

If you pulled the Team or Enterprise JSON export, do not expect a documented schema. Zapier does not publish the exported-JSON field map, and a community thread asking for one got no answer; one participant called the export "all very cryptic". Match app and action-name strings defensively instead of assuming fixed keys.

# The export schema is undocumented: match step-name strings, not keys
grep -ic "conversation with assistant (legacy)" zap-export.json
grep -ic "summarize text (legacy)" zap-export.json
grep -ic "create assistant" zap-export.json

Or skip the manual grep: the free Zapier readiness scan checks your steps against the full deprecated list without a signup, and detection is never paywalled.

Create Assistant and vector-store steps: no direct replacement#

Zapier's notice lists a second group of affected steps with no named target: the actions Create Assistant, Upload File (assistants), Create Vector Store, and Create Vector Store File; the searches Find Assistant and Find or Create Assistant; and the dropdowns List Assistants, List Vector Stores, and List Assistant Files.

These steps existed because the Assistants API made you build and manage a persistent assistant with its own files and vector stores. The Conversation action folds file search and file tools into the step itself, so a Zap that ran Create Vector Store and then Conversation With Assistant does not get a one-for-one swap. It gets redesigned, usually into fewer steps built around Conversation.

Common mistakes that surface after the swap#

• Skipping the downstream remap. The replacement action's output fields differ, so downstream steps still point at fields from the deleted step until you re-map them.
• Waiting for an automatic migration. Zapier's notice is explicit that affected Zaps must be rebuilt by hand.
• Matching step names case-sensitively. Zapier's own pages disagree on "With" versus "with", so strict string matching misses real steps.
• Assuming the exported JSON has a stable, documented schema. It does not; search for app and action-name strings anywhere in the file.
• Bundling the AI Actions / NLA wind-down into this deadline. That track has no published shutdown date and is a separate migration to Zapier MCP.