Automation, AI and developer platforms that are closing

API calls to these model IDs fail after their shutdown dates, and the listed fine-tuned models are removed on 2026-10-23.

Key dates

• October 23, 2026: first batch stops working (gpt-3.5-turbo, gpt-4, gpt-4-turbo, gpt-4-1106-preview, gpt-4.1-nano, gpt-4o-2024-05-13, o1, o1-pro, o3-mini, o4-mini, gpt-image-1, and fine-tunes of gpt-3.5-turbo, gpt-4, gpt-4.1-nano, babbage-002 and davinci-002)
• December 1, 2026: image models stop working (gpt-image-1-mini, gpt-image-1.5, chatgpt-image-latest)
• December 11, 2026: GPT-5 and o3 2025 snapshots stop working (gpt-5-2025-08-07, gpt-5-mini-2025-08-07, gpt-5-nano-2025-08-07, gpt-5-pro-2025-10-06, o3-2025-04-16, o3-pro-2025-06-10)
• April 1, 2027: GPT-5.1 and others stop working (gpt-5.1, gpt-5.3-codex, gpt-5.4-nano)

Data deleted

Not announced. No account data deletion is announced for base models. The listed fine-tuned versions are removed on 2026-10-23; the notice does not say what happens to their training files

Where to move

• Official: switch to the substitutes OpenAI lists per model (gpt-5.6-sol, gpt-5.6-terra or gpt-5.6-luna for text; gpt-image-2.5-sunburst or gpt-image-2.5-flare for images; gpt-6-sol or gpt-6-luna for gpt-5.1, gpt-5.3-codex, gpt-5.4-nano)
• Re-test prompts, structured output and tool calls after switching; pin dated snapshots
• Or point the same automation step at another provider (Anthropic, Google Gemini)

Good to know

Batches announced 2026-04-22 (Oct 23 shutdown), 2026-06-02 (images), 2026-06-11 (GPT-5/o3) and 2026-10-01 (GPT-5.1 etc.). Older n8n/Zapier/Make workflows that hard-code gpt-3.5-turbo, gpt-4 or gpt-4-turbo fail from 2026-10-23. The Dec 11 notice lists dated snapshots only and does not say what happens to undated aliases such as gpt-5, gpt-5-mini or o3, so check which snapshot your alias resolves to. Separately, existing customers can no longer create new fine-tuning jobs from 2027-01-06.

Sources

developers.openai.com

Pipelines v1 and v1 OAuth calls stop working on their sunset dates, new legacy private apps cannot be created, and all /v1-/v3 endpoints plus legacy apps lose support in September 2027.

Key dates

• October 26, 2026: no new legacy private apps (for existing accounts; new accounts lost the option on 2026-09-28)
• December 4, 2026: Pipelines API v1 stops working
• February 16, 2027: v1 OAuth API stops working (POST /v1/token and the access and refresh token lookup and delete endpoints)
• March 30, 2027: v4 APIs lose support
• September 2027: v1-v3 APIs and legacy apps lose support

Data deleted

No. No CRM data is deleted; integrations break or lose support

Where to move

• Official: migrate straight to date-based versioned (DBV) APIs, e.g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token, /introspect, /revoke
• Official: Service Keys for new private integrations; Projects-based model for public and private apps
• Update HubSpot steps in Zapier, Make, n8n or custom code once the connector supports the new versions

Good to know

Pipelines v1 sunset announced 2026-08-14; v1 OAuth deprecation announced 2026-05-12. Unsupported means no bug fixes, reliability or security updates; marketplace apps on v1-v4 after September 2027 lose certification. HubSpot says per-endpoint replacement docs arrive with the March 2027 release. Any integration that exchanges or refreshes tokens through the v1 OAuth API must switch before 2027-02-16.

Sources

developers.hubspot.comdevelopers.hubspot.comdevelopers.hubspot.commartechnotes.com

The Pinpoint console, endpoints, segments, campaigns, journeys, in-app messaging, recommenders and analytics/KPI APIs go away; push, OTP and phone-number validation continue, and SMS/voice/email sending continues for existing customers.

Key dates

• May 20, 2025: closed to new customers
• October 30, 2026: engagement features end (console, endpoints, segments, campaigns and journeys no longer accessible)

Data deleted

Not announced. AWS says resources become inaccessible and tells customers to export endpoints (segment export), segments, campaigns and journeys (get-* APIs), templates and up to 3 months of KPIs first; no deletion date is stated

Where to move

• Official: Amazon Connect outbound campaigns and Customer Profiles for engagement
• Official: AWS End User Messaging (SMS, voice, push), Amazon SES (email), Amazon Kinesis (events)
• Engagement SaaS (Braze, Customer.io, OneSignal) or simple journeys rebuilt in n8n calling SES / End User Messaging

Good to know

SendMessages, SendOTPMessage and event delivery to Kinesis/Firehose/CloudWatch keep working; SendUsersMessages and sending to stored endpoint IDs do not. n8n is realistic only for simple campaign/journey logic, not high-volume segmentation.

Sources

docs.aws.amazon.compushwoosh.com

The visual Agent Builder, hosted workflow IDs run through ChatKit, the Evals platform and the v1/prompts API. ChatKit, the Agents SDK and the Responses API stay.

Key dates

• October 31, 2026: existing evals become read-only
• November 30, 2026: Agent Builder, Evals and v1/prompts shut down

Data deleted

Not announced. OpenAI publishes no export or deletion details for workflow definitions, prompts or eval results, so copy them before the dates

Where to move

• Official: Agents SDK (code export) or ChatGPT Workspace Agents
• Official: Promptfoo for Evals; inline the prompt text for reusable prompts
• n8n (AI Agent node), Langflow or Dify

Good to know

Automations that call the Responses API with a dashboard prompt ID (suggested in Make community threads as an Assistants API replacement) break on 2026-11-30 unless the prompt text is inlined.

Sources

developers.openai.comdevelopers.openai.com

Apiary Standard and Professional (API Blueprint design, docs and mocks) can no longer be used.

Key dates

• October 31, 2026: shut down, instances deleted

Data deleted

Yes. Oracle: all remaining instances will be permanently deleted after the EOL date

Where to move

• Official: convert API Blueprint to OpenAPI, then move to Apimatic, Postman, Swagger Editor, Stoplight, Redocly or Bump.sh

Good to know

Anything published on apiary.io (docs, mock endpoints) depends on the service, so export specs and set up replacement docs before 2026-10-31. Oracle API Platform Cloud Service reaches EOL the same day (announced 2025-10-27).

Sources

docs.oracle.com

From 2027-07-29 new functions cannot use deprecated runtimes and from 2027-08-31 their code and configuration cannot be updated; existing functions can still be invoked.

Key dates

• October 31, 2026: python3.10 deprecated (no more security patches or support)
• November 10, 2026: dotnet8 deprecated
• April 30, 2027: nodejs22.x deprecated
• July 29, 2027: no new functions on deprecated runtimes
• August 31, 2027: no updates to functions on deprecated runtimes

Data deleted

No. Functions are not deleted; deprecated runtimes get no security patches

Where to move

• Official: upgrade to a supported runtime (nodejs24.x, python3.12-3.14, java21/java25, dotnet10, provided.al2023)
• Move small glue or cron functions that are not worth upgrading to a workflow tool or another FaaS

Good to know

AWS calls the dates forecasts that are subject to change. The Jul 29 / Aug 31, 2027 blocks apply to nearly every deprecated runtime (nodejs16.x/18.x/20.x, python3.8/3.9, etc.).

Sources

docs.aws.amazon.com

Heroku-22 apps cannot be built or deployed from 2027-05-01 (they keep running); the platform gets no new features and no Enterprise contracts for new customers.

Key dates

• November 1, 2026: Heroku-22: first build every 30 days fails
• February 1, 2027: Heroku-22: first build every 7 days fails
• April 1, 2027: Heroku-22: first build every 24 hours fails
• April 30, 2027: Heroku-22 end of life
• May 1, 2027: no builds or deploys on Heroku-22

Data deleted

No. Apps are not shut down; Heroku has set no end-of-life date for the platform

Where to move

• Official: upgrade apps to the Heroku-24 stack
• Longer term: Render, Railway, Fly.io, a hyperscaler, or self-hosting
• Heroku Scheduler jobs that are really automations can move to a workflow tool

Good to know

Sustaining engineering = stability, security, reliability and support only. Existing Enterprise subscriptions are honored and can renew; pay-as-you-go customers continue unchanged.

Sources

heroku.comhelp.heroku.comsimonwillison.net

Rules and Hooks stop running, so login-pipeline logic and the side effects they trigger (profile enrichment, webhooks, notifications) stop.

Key dates

• November 18, 2024: read-only
• November 18, 2026: Rules and Hooks stop running and are removed

Data deleted

Yes. Auth0 says Rules and Hooks are removed at end of life; keep your own copy of the code

Where to move

• Official: Auth0 Actions (Migrate from Rules to Actions / Migrate from Hooks to Actions guides)
• Move non-blocking side effects (CRM sync, chat alerts) to Auth0 log streams or webhooks handled by an integration tool

Good to know

The same Auth0 page lists end of life for Uncapped User Profile Data on 2027-03-04.

Sources

auth0.com

Requests to claude-sonnet-4-5-20250929 fail on Anthropic-operated platforms.

Key dates

• November 30, 2026: retired, requests fail

Data deleted

No. Model retirement only

Where to move

• Official: claude-sonnet-5-5
• Re-test prompts and tool calls; Claude 4.7 and later models return a 400 error for a non-default temperature, top_p or top_k

Good to know

Dates apply to the Claude API, Claude Platform on AWS and Microsoft Foundry; Amazon Bedrock and Google Cloud set their own schedules.

Sources

platform.claude.com

Apps, scripts, devices and automations that send mail through Exchange Online SMTP AUTH with a username and password are rejected unless an admin re-enables Basic auth.

Key dates

• December 2026: Basic auth for SMTP AUTH off by default (admins can re-enable it for existing tenants; new tenants can't use it)

Data deleted

No. Authentication change only

Where to move

• Official: OAuth 2.0 for SMTP AUTH
• Microsoft Graph sendMail
• A third-party SMTP relay (Amazon SES, SendGrid, Mailgun)

Good to know

Microsoft says end of December 2026. The final removal date will be announced in the second half of 2027.

Sources

techcommunity.microsoft.comoffice365itpros.com

Accelerate is retired, including Prisma Postgres connections routed through it; query caching (cacheStrategy) has no replacement.

Key dates

• December 1, 2026: Accelerate retired

Data deleted

No. Prisma says your database, your data and your plan stay as they are; only the connection changes

Where to move

• Official: switch to a pooled connection or the serverless driver
• Official: keep your own database and connect without Accelerate, or move to Prisma Postgres
• Remove cacheStrategy from queries before switching

Good to know

The same changelog says Prisma Postgres Early Access databases are deleted on 2026-11-01.

Sources

prisma.io

The Essential and legacy bot experiences are removed; Zendesk migrates bots that customers have not moved to the upgraded AI agent experience, with some exceptions.

Key dates

• August 31, 2026: legacy experience in maintenance mode
• January 2027: Essential AI agents migrated
• February 2027: legacy AI agents migrated

Data deleted

No. Bots are migrated rather than deleted (Zendesk notes exceptions)

Where to move

• Official: migrate to the upgraded AI agent experience (capabilities formerly in the AI agents - Advanced add-on) using the Zendesk per-feature migration guides
• Zendesk Professional Services

Good to know

Pricing is tied to automated resolutions, so costs can change after migration. Earlier versions of the notice used a different removal date; the version edited 2026-09-30 uses forced migration in January/February 2027.

Sources

support.zendesk.comgetmacha.com

The Custom Search JSON API (already closed to new customers) stops for existing customers, and existing engines lose whole-web search.

Key dates

• January 20, 2026: new engines limited to 50 sites
• January 1, 2027: JSON API stops for existing customers (existing engines also lose whole-web search)

Data deleted

No. No user data involved; the endpoint stops serving results

Where to move

• Official: Vertex AI Search (up to 50 domains) or contact Google about its full web search solution
• Third-party web search APIs (Brave Search API, SerpAPI, Tavily, Exa)
• Search grounding built into model APIs (Gemini, OpenAI, Anthropic web search tools)

Good to know

Often used as the Google search tool in AI-agent and research automations; replace it before late December 2026.

Sources

developers.google.comprogrammablesearchengine.googleblog.combrave.com

Text-to-speech, transcription/translation and older realtime/audio models are removed from the API on these dates.

Key dates

• January 6, 2027: text-to-speech models stop working (tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20, gpt-4o-mini-tts-2025-12-15)
• January 20, 2027: realtime and audio models stop working (gpt-realtime, gpt-audio, gpt-4o-audio, gpt-4o-realtime and their mini variants)
• February 26, 2027: transcription models stop working (whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, gpt-4o-transcribe-diarize and /v1/audio/translations)

Data deleted

No. Model retirement only

Where to move

• Official: gpt-realtime-2.1-mini (TTS); gpt-live-transcribe or gpt-transcribe (transcription); v1/realtime/translations; gpt-realtime-2.1 or gpt-audio-1.5 (realtime/audio)
• Other speech APIs (Deepgram, AssemblyAI, ElevenLabs, Google Cloud, Azure AI Speech)

Good to know

Check transcription and text-to-speech steps in automations; OpenAI points TTS users to a Realtime model, so a plain text-in, audio-file-out step may need rework.

Sources

developers.openai.com

gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14, plus fine-tunes on them, are removed from the API.

Key dates

• January 14, 2027: stops working, fine-tunes included

Data deleted

Not announced. Fine-tuned versions follow the base-model shutdown; nothing is said about training files

Where to move

• Official: gpt-6-luna
• Re-test structured output and function calling before switching
• Or another provider model

Good to know

These models are widely used in chatbot and AI-agent workflows, so audit model fields in every automation tool.

Sources

developers.openai.com

After 2027-01-31 Connect gets only critical security fixes and Atlassian expects breakages to grow; apps are not switched off on that date.

Key dates

• March 31, 2026: no Connect app updates or new private installs
• January 31, 2027: Connect end of support

Data deleted

No. No deletion announced; apps degrade over time

Where to move

• Official: migrate or rebuild the app on Forge
• For simple webhook/REST integrations: Jira/Confluence webhooks and REST API driven from an integration tool

Good to know

End of support moved to 2027-01-31 in the Atlassian post of 2026-08-03 (older secondary pages still say Q4 2026).

Sources

atlassian.comatlassian.compraecipio.com

The Notify API (bulk SMS fan-out and push notifications through bindings) stops for existing customers.

Key dates

• January 31, 2027: end of life for existing customers

Data deleted

Not announced. Twilio does not say what happens to Notify bindings or other stored data

Where to move

• Official: Programmable Messaging/SMS API (with message scheduling) or the Bulk Messaging API for SMS
• Official: Verify (push authentication), Conversations, Segment with push partners; Push API private beta
• Notification services such as Courier, Knock, OneSignal

Good to know

Twilio's pages disagree: a January 2024 changelog post said end of life 2025-12-31, while the support article (updated 2025-07-09) says 2027-01-31. Confirm with Twilio.

Sources

support.twilio.comtwilio.comcourier.com

Firebase Studio workspaces stop; core Firebase services (Cloud Firestore, Authentication, App Hosting) keep working.

Key dates

• June 22, 2026: no new workspaces or signups
• March 22, 2027: shut down, data deleted

Data deleted

Yes. All remaining Firebase Studio data is permanently deleted on 2027-03-22 and cannot be recovered

Where to move

• Official: Google Antigravity (code-first) or Google AI Studio (browser prototyping)
• Official export: the Move now button or npx firebase-tools@latest studio:export PATH
• Other cloud IDEs or AI app builders (GitHub Codespaces, Replit)

Sources

firebase.google.com

Calls to these v0 operations stop working, breaking order and settlement syncs that still use them.

Key dates

• March 27, 2027: Orders API v0 operations removed (getOrders, getOrder, getOrderBuyerInfo, getOrderAddress, getOrderItems, getOrderItemsBuyerInfo)
• August 27, 2027: Finances API v0 operations removed (listFinancialEvents, listFinancialEventsByGroupId, listFinancialEventsByOrderId)

Data deleted

No. API removal only

Where to move

• Official: move to the current Orders and Finances API versions per the SP-API deprecation schedule and migration guides
• Update Amazon Seller steps in Make, Zapier, n8n or custom code

Good to know

Orders v0 was deprecated 2026-01-28 and Finances v0 on 2025-07-21.

Sources

developer-docs.amazonhelp.make.com

Every Pipedream workflow and String stops running. Pipedream Connect (Connect API, MCP servers, API Proxy) is not affected.

Key dates

• September 30, 2026: signups and new subscriptions closed
• March 31, 2027: stops working (subscriptions cancelled with a prorated refund)
• April 30, 2027: all data deleted

Data deleted

Yes. All Workflows data is permanently deleted, including credentials and OAuth tokens of connected accounts. Data store records and File Store files are not in the official export, so copy them first

Where to move

• Official: the Export Workflows tool (JSON, secret values redacted)
• n8n (cloud or self-hosted)
• Make, Zapier, Activepieces, Windmill or plain serverless code

Good to know

Secret values are redacted in the export, so credentials must be re-entered in the new tool.

Sources

pipedream.compipedream.com

The Deno Deploy hosting service and everything running on it stop; the open-source Deno runtime gets one more year of fixes, then official development ends.

Key dates

• July 20, 2026: Deploy Classic and Subhosting v1 API shut down
• April 2027: Deno Deploy shuts down (six months after the 2026-10-09 announcement; exact day not published)
• October 2027: official Deno runtime development ends (after a year of monthly bug-fix and security releases)

Data deleted

Not announced. The announcement does not say how long hosted data (for example Deno KV) stays exportable

Where to move

• Official: Cloudflare Workers (migration support for paying customers)
• Other serverless hosts (Vercel, Netlify, Fly.io, AWS Lambda)
• Cron and webhook scripts can move to a workflow tool

Good to know

Only "six months" is official, so the date has month precision (about 2027-04-09). JSR keeps running on Cloudflare infrastructure.

Sources

deno.comdocs.deno.comhighcircl.com

All EWS requests to Exchange Online are blocked; on-premises Exchange Server is not affected.

Key dates

• August 2026: deadline to opt in (set EWSEnabled=True and an AppID allow list)
• October 1, 2026: EWS off by default (for tenants that did not opt in; admins can re-enable it)
• April 1, 2027: EWS permanently disabled

Data deleted

No. API shutdown only; mailbox data stays

Where to move

• Official: Microsoft Graph
• Update or replace third-party tools that still use EWS (backup, archiving, CRM and email sync)
• Rebuild in-house EWS scripts as Graph-based automations (n8n Microsoft Outlook node, Power Automate)

Good to know

Since October 2026, with EWSEnabled=True only apps on the AppID allow list can call EWS. n8n is realistic for in-house mailbox automations, not for replacing third-party products.

Sources

techcommunity.microsoft.comlearn.microsoft.combleepingcomputer.com

Opsgenie (alerting, on-call, escalations and its APIs/integrations) is shut off and no longer accessible.

Key dates

• June 4, 2025: end of sale
• April 5, 2027: shut down, data deleted

Data deleted

Yes. Data not moved to Jira Service Management (or downloaded) is deleted on 2027-04-05

Where to move

• Official: Jira Service Management (or Compass, which lacks stakeholder management)
• PagerDuty, incident.io, Better Stack, Squadcast

Good to know

Re-point monitoring tools and automations that create Opsgenie alerts through its API or webhooks.

Sources

atlassian.comatlassian.comhyperping.com

Zendesk Sell and its mobile app stop working.

Key dates

• August 31, 2027: retired, data deletion starts

Data deleted

Yes. Data is deleted when the subscription ends or from 2027-08-31, whichever comes first; activity history, appointments, emails, call logs and documents cannot be exported

Where to move

• Official partner: Pipedrive (migration tools, native Zendesk integration)
• Other CRMs (HubSpot, Salesforce, Zoho CRM)
• Export leads, contacts, deals, notes, tasks and smart lists via Settings > Data > Export (CSV)

Good to know

Export files stay in the Export panel for 30 days. Automations that use Sell as a trigger or action must be re-pointed to the new CRM.

Sources

support.zendesk.comsalesforceben.com

Official development, fixes and security patches have ended; self-hosted installs keep running without upstream updates.

Key dates

• July 29, 2026: code freeze
• August 10, 2026: repo archived (npm packages and Docker images marked deprecated)
• August 31, 2026: end of life

Data deleted

Not announced. Self-hosted data stays where it is; Flowise has published no Flowise Cloud shutdown or deletion date

Where to move

• Official: fork the Apache-2.0 repo and maintain it, or use a community fork
• n8n (AI Agent and LangChain nodes)
• Langflow, Dify

Good to know

Self-hosted users are left without security fixes. Third-party claims of a specific Flowise Cloud shutdown date are unverified.

Sources

flowiseai.comgithub.comusecarly.com

The Assistants API (assistants, threads, runs) has been removed, so automations built on assistant IDs no longer work.

Key dates

• August 26, 2026: removed from the API

Data deleted

Not announced. The OpenAI notice does not say whether stored threads or files can still be retrieved

Where to move

• Official: Responses API plus Conversations API (Assistants-to-Conversations migration guide)
• Agents SDK
• Rebuild as an agent in n8n (AI Agent node) or Make

Good to know

If you replaced Assistants with dashboard prompt IDs, those reusable prompts shut down on 2026-11-30.

Sources

developers.openai.comcommunity.openai.comcommunity.make.com

Messages sent to Teams through Office 365 Connectors, including Incoming Webhook URLs, are no longer delivered.

Key dates

• May 18, 2026: final retirement rollout starts
• May 22, 2026: connectors and incoming webhooks stop working

Data deleted

No. Past channel messages stay; only delivery stops

Where to move

• Official: Workflows app in Teams (Power Automate) with Workflows webhooks
• A Teams bot or Microsoft Graph channel messages
• n8n Microsoft Teams node or another automation tool posting via Graph

Good to know

The date moved several times before the final rollout of May 18-22, 2026. CI/CD and monitoring alerts that used webhook URLs need new endpoints.

Sources

devblogs.microsoft.comlearn.microsoft.com

SharePoint 2013 workflows can no longer be created or run in SharePoint Online.

Key dates

• April 2, 2024: off for new tenants
• April 2, 2026: workflows stop running in existing tenants

Data deleted

No. Existing workflows can still be viewed as raw XML files after the turn-off

Where to move

• Official: Power Automate
• Official: Approvals in Lists and Document Libraries for simple approvals
• Third-party tools that use SharePoint APIs (n8n, Nintex, FlowForma)

Good to know

Teams that never rebuilt these workflows can read the XML definitions to recreate the logic.

Sources

support.microsoft.comflowforma.com