Deadline: August 26, 2026
Replace legacy ChatGPT/OpenAI Zapier steps before August 26, 2026
OpenAI is sunsetting the Assistants API. Zapier has deprecated the ChatGPT steps that relied on it. If your Zaps use Conversation With Assistant, Create Assistant, vector stores, or Assistant lookups, they stop working on August 26, 2026 unless you migrate to Responses API-backed actions. We map the old actions to the four replacement actions, handle memory and file-search remaps, and test downstream fields so the bot keeps working after the cutoff.
Deprecated steps to inventory
Open these Zaps first:
- Conversation With Assistant (Legacy) — stateful chat against an Assistant/Thread.
- Create Assistant — replaced by Prompt objects in the OpenAI dashboard or inline system instructions.
- Upload File (when used with assistants) and Create Vector Store / Create Vector Store File — replaced by the Responses API File Search tool and dashboard-managed vector stores.
- Find Assistant and Find or Create Assistant — no direct API equivalent; use manual Prompt IDs or inline instructions.
The four Responses API replacement actions
Zapier surfaces the new OpenAI Responses API as:
- Conversation (Responses API) — for stateful chat with memory keys and tool support.
- Analyze Text — replaces Summarize Text, Classify Text, and Analyze Text Sentiment.
- Analyze Images — replaces vision-based legacy image analysis.
- Extract Structured Data — replaces JSON/structured-output extraction.
Stateless single prompts can also use Send Prompt. The right choice depends on whether the old step relied on Assistant memory, file search, tools, or just a one-off prompt.
Not a model swap
The hidden work is an architecture migration, not a prompt rewrite. Assistant objects become dashboard Prompts or inline system messages. Threads become conversations. Runs become responses. Vector stores move to the File Search tool or the OpenAI dashboard. A Zap can test the new action and still fail later because the output shape or memory behavior changed.
Common migration risks
- Assistant IDs: any Zap that stores or passes an Assistant ID needs a new memory key or Prompt ID strategy.
- Thread IDs: thread state moves to Memory Keys in Zapier or conversation IDs in n8n.
- File search / vector stores: vector store creation through the API is gone; file search is now managed through the File Search tool or OpenAI dashboard.
- Output fields: downstream steps that consumed old Assistant output must be remapped to the new response shape.
- Tools and functions: custom tool loops may need explicit tool-call handling in Zapier or an n8n fallback.
The Mimir Works migration
We run a four-phase rescue before August 26:
- Inventory: export affected Zaps and tag each deprecated step by replacement type.
- Design: choose inline vs dashboard Prompts, map memory keys, and rebuild file search indexes.
- Rebuild: replace deprecated steps, remap downstream fields, and test in isolation.
- Cutover: schedule the switch, monitor the first 48 hours, and archive old Zaps only after stable runs.
Deliverables and pricing
- Migration kit: $99 — inventory worksheet, action replacement map, field-remap sheet, memory/file-search patterns, QA checklist.
- Light DFY migration: $500 — up to 5 simple legacy Zaps.
- Standard DFY migration: $950 — up to 10 Zaps with memory and file search.
- Full DFY migration: $1,500 — up to 20 Zaps plus dashboard Prompt setup, vector store rebuild, and 30-day support.
- Consulting call: $150 — 60-minute call to review your Zap inventory and pick replacements.
Start with the smallest proof
Send the old action names from your Zap editor plus whether you use Assistant IDs, Thread IDs, or vector stores. We will sort each step into the right replacement path — Zapier Responses action, dashboard Prompt, or n8n fallback — before you buy anything.