OpenAI Agent Builder shuts down on 30 November. What should small teams switch to?

When does OpenAI Agent Builder shut down?

On 30 November 2026. OpenAI announced the change on 3 June 2026 on its API deprecations page, together with two related shutdowns. If you built an agent in Agent Builder, it needs a new home within the next five weeks.

OpenAI points Agent Builder users to two replacements: the Agents SDK, or Workspace Agents in ChatGPT. For reusable prompts, its advice is to move the prompt content into your own application code.

What are the alternatives to OpenAI Agent Builder?

There are two official routes and several independent ones. These four cover most small teams:

A few facts behind that table. OpenAI's migration guide describes the Agents SDK as "best for building agents through code" and Workspace Agents as "best for building agents through natural language and sharing them with teams". OpenAI says workspace agents run in the cloud, can run on a schedule, can be deployed in Slack, and can be set to ask permission before sensitive steps such as sending an email. Zapier's help centre says its agents can be given triggers, actions and knowledge sources, and that Zapier is moving Agents into "AI by Zapier". Hostinger's n8n tutorial shows the AI Agent node working with OpenAI or Google Gemini models, with memory and tool sub-nodes, on a self-hosted server.

Which alternative should a small team pick?

Our advice is to decide by where the agent lives and who talks to it, not by which tool has the longest feature list.

1. 1Customers talk to it on your website? Use the Agents SDK in your own site or app. Of OpenAI's two official routes, it is the one meant for agents inside your own product.
2. 2Only your team uses it, inside ChatGPT or Slack? Use Workspace Agents, if you already pay for a Business or Enterprise workspace.
3. 3It mostly moves information between apps? Zapier or n8n will usually be simpler than code.
4. 4Data has to stay on your own servers? Self-hosted n8n or the Agents SDK.
5. 5Not sure the agent is still worth running? Switch it off. A shutdown is a good moment to cut automations nobody checks.

Worked example: moving an enquiry agent before 30 November

This is a hypothetical scenario, not a client. A small property agency in Dubai built one Agent Builder workflow. It reads each website enquiry, tags it as buy, rent or sell, drafts a reply for the agent, and posts a summary to the team's Slack channel.

1. 1Write down what it does today. List every step, every tool it calls and every prompt. Save ten to twenty real past enquiries with the outputs the team was happy with. These are your test cases, so copy them before the Evals dashboard goes read-only on 31 October.
2. 2Split the job in two. The reply draft touches customers. The Slack summary is internal. They do not need to live in the same tool.
3. 3Export the customer part to code. In Agent Builder, open the workflow, choose Code, select Agents SDK and copy the TypeScript or Python export, as OpenAI's guide describes. A developer adds it to the website's backend and moves any reusable prompts into the code.
4. 4Rebuild the internal part as a workspace agent. Describe the summary job in ChatGPT, connect Slack, and require approval before anything is sent outside the team.
5. 5Test against the saved cases. Run the twenty old enquiries through both new versions and compare the results with the originals, which is the check OpenAI's guide recommends.
6. 6Run old and new side by side for a week, then switch the old workflow off before 30 November rather than on it.

Total risk: one quiet week of overlap. The alternative is finding out on 1 December that enquiries stopped being tagged.

What does this shutdown teach you about building on AI platforms?

AI platforms change fast, and not only at OpenAI. Pipedream, for example, has closed sign-ups for its Workflows product and says workflows will stop on 31 March 2027, with data deleted by 30 April 2027.

Our advice: keep the parts that hold your business logic in files you own. That means prompts in your codebase or documents, test cases in a folder, and a short written description of what each automation does. Then the next shutdown is a migration, not a rebuild.

If you want a second pair of hands, our AI workflows service maps what you run today and moves it to a setup your team can maintain. If the agent lives on your website, our Next.js development team can build it into the site.

Sources

• Deprecations (OpenAI API docs, accessed 26 October 2026)
• Migrate from Agent Builder (OpenAI API docs, accessed 26 October 2026)
• Introducing workspace agents in ChatGPT (OpenAI, 22 April 2026)
• Zapier Agents (Zapier Help Center, 1 October 2026)
• How to build an AI agent with n8n (Hostinger, 18 August 2026)
• Workflows and String are shutting down on March 31, 2027 (Pipedream docs, accessed 26 October 2026)