OpenAI is closing Agent Builder, its drag-and-drop canvas for multi-step agent workflows. According to OpenAI's own documentation, the product is scheduled to shut down on November 30, 2026. If you built a support bot, a research helper or an internal workflow on it, you have about four weeks to move it.
This guide covers what is actually changing, how to export a workflow the way OpenAI recommends, and eight OpenAI Agent Builder alternatives, from OpenAI's own Agents SDK to no-code tools like n8n and Zapier. Everything here comes from OpenAI's developer docs and the vendors' own pages, checked on November 1, 2026.
QUICK ANSWER
OpenAI announced Agent Builder's deprecation on June 3, 2026, and it is scheduled to shut down on November 30, 2026. ChatKit stays available. To migrate, open each workflow, click Code, choose Agents SDK, copy the TypeScript or Python export, and run it with the Agents SDK or paste it into a ChatGPT workspace agent.
What is changing and when
OpenAI's Agent Builder guide now opens with a notice: the product is being deprecated, existing users can keep using it during a transition window, and it is scheduled to shut down on November 30, 2026. The OpenAI deprecations page adds the timeline: developers were notified on June 3, 2026.
| Date | What happens |
|---|---|
| June 3, 2026 | Deprecation announced to Agent Builder users |
| Now to Nov 29, 2026 | Transition window: existing workflows keep working |
| Nov 30, 2026 | Agent Builder scheduled to shut down |
What stays
ChatKit, OpenAI's toolkit for embedding chat experiences in a website or app, remains available. So does the Agents SDK, the code library that Agent Builder could already export to. What goes away is the visual canvas itself, along with its node editor, templates and in-canvas preview and evaluation.
How to export your workflow before Nov 30
OpenAI's migration guide describes one export path, and it's quick:
- Open the workflow in Agent Builder.
- Select Code in the top navigation.
- Select Agents SDK in the code dialog.
- Choose TypeScript or Python and copy the complete export.
Do this for every workflow, including old versions you might need, and save the code somewhere safe such as a private Git repository. Also copy each agent's instructions, tool settings and any guardrail text into a document. OpenAI is clear that the export "does not convert your workflow graph or guarantee that every behavior transfers unchanged", so you want a record of how things worked.
Two official destinations
- Agents SDK: paste the export into your own application, install the matching SDK, and test it in your runtime. Best if you have a developer.
- ChatGPT workspace agents: if you have a ChatGPT Business, Enterprise or Edu workspace with agent access, create a workspace agent and paste the exported code into the chat, asking it to convert the workflow. Best for teams that want to keep building in plain language.
OpenAI warns that workflows with "strong determinism at their core" may not migrate faithfully to a workspace agent, and that apps, authentication and permissions need a separate review.
8 OpenAI Agent Builder alternatives
Not everyone wants to stay inside OpenAI. These are the most practical replacements, grouped by who they suit. Check each vendor's current pricing before you commit, because plans change often.
1. OpenAI Agents SDK (code, official path)
The closest like-for-like move, since Agent Builder already exports to it. Available for Python and TypeScript. You host and run it yourself, which also means you own logging, retries and deployment.
2. ChatGPT workspace agents (no code, official path)
Good for internal team assistants that live inside ChatGPT. Less suited to customer-facing bots embedded on your website.
3. n8n (visual, self-hostable)
A node-based workflow tool with dedicated AI agent features. It feels closest to Agent Builder's canvas, connects to hundreds of apps and can be self-hosted, which matters if you handle sensitive data.
4. Zapier Agents (no code)
Zapier's agent product builds on its huge library of app integrations. A strong choice for small businesses whose workflows are mostly "when X happens in one app, do Y in another".
5. Make (visual scenarios)
Make offers AI agents alongside its visual scenario builder. It's popular with marketers and operations teams who like seeing every step mapped out.
6. Microsoft Copilot Studio (enterprise)
Microsoft's low-code agent builder, a natural fit if your company already runs on Microsoft 365, Teams and SharePoint, with admin controls IT departments expect.
7. Langflow (open source, visual)
An open-source visual builder for agents and retrieval workflows. Works with many model providers, so you aren't locked to one AI company.
8. Flowise (open source, visual)
Another open-source drag-and-drop builder for chatbots and agents, easy to self-host on a small server.
Which should you pick?
| If you... | Start with |
|---|---|
| Have a developer and want the least rework | Agents SDK |
| Only need internal team helpers in ChatGPT | Workspace agents |
| Want a visual canvas and self-hosting | n8n, Langflow or Flowise |
| Mostly connect business apps | Zapier or Make |
| Live in Microsoft 365 | Copilot Studio |
Step by step: rebuild your agent instructions with a free tool
Whatever platform you move to, the part that transfers best is your agent's instructions. Rewriting them cleanly is the fastest way to get the same behaviour on a new tool. Our free System Prompt Builder helps you do that in the browser, with no AI call and nothing saved.
- Paste your old instructions from the Agent Builder export into a notes file, so you can see them side by side.
- Open the System Prompt Builder and fill in the role (for example, "You are a support agent for a UK online bike shop") and the audience.
- Set tone, length and format, such as short paragraphs or step-by-step answers.
- Add the rules your old agent followed: ask clarifying questions, admit uncertainty, never invent order details, hand off to a human for refunds.
- Copy the generated prompt into your new platform's agent instructions field, then test it with the same sample questions you used in Agent Builder's preview.
If your workflow returned structured data, check the new output with our JSON Formatter, and use the AI API Cost Calculator to estimate running costs on your new setup.
Migration checklist
- List every published workflow and where it's used (website widget, internal tool, API).
- Export each one as Agents SDK code and store it in version control.
- Record tools, file search sources, connected apps and API keys each workflow relied on.
- Pick a destination per workflow; you don't need one tool for everything.
- Re-test with real sample inputs and compare answers with the old version.
- Review safety: prompt injection and data leakage risks don't disappear when you change platforms. Our guide to AI agent attacks on small businesses lists the basics.
- Switch traffic over well before November 30, and keep the old export as a backup.
Choosing the underlying model again? Our comparison of ChatGPT vs Gemini vs Claude can help, and the open-source Garuda coding agent shows another way to run agents with your own model.
Related: If your agents work on code, GitHub Agentic Workflows is another option worth a look.
Sources and further reading
- Agent Builder (OpenAI)
- Deprecations (OpenAI)
- Migrate from Agent Builder (OpenAI)
- OpenAI Agents SDK (OpenAI)
FAQ
When does OpenAI Agent Builder shut down?
OpenAI's documentation says Agent Builder is scheduled to shut down on November 30, 2026. The deprecation was announced to developers on June 3, 2026.
Is ChatKit also shutting down?
No. OpenAI says ChatKit remains available.
How do I export an Agent Builder workflow?
Open the workflow, select Code, choose Agents SDK, pick TypeScript or Python and copy the complete export.
Will my workflow work exactly the same after migrating?
Not guaranteed. OpenAI says the export does not convert the workflow graph or guarantee every behavior transfers unchanged, so test with real inputs.
What is the best no-code alternative to Agent Builder?
It depends on your stack. n8n is closest to a visual canvas and can be self-hosted, Zapier and Make suit app-to-app automation, and Copilot Studio suits Microsoft 365 companies.
Comments
Post a Comment