VapiAI · bets-margulies-vapi · Jun 27, 2026
diff --git a/fern/workflows.mdx b/fern/workflows.mdx
@@ -4,14 +4,20 @@ subtitle: Break down AI conversations into a visual workflow made up of discrete
 slug: workflows
 ---
 
-<Success intent="launch">
-  Workflows is now available to all Vapi users in Open Beta on [the dashboard here](https://dashboard.vapi.ai/workflows). Start building more reliable and structured conversational AI today. 
-</Success>
+<Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
+We no longer recommend Workflows for new builds. Prefer **Assistants** or **Squads** depending on complexity. See [Assistants](/assistants/dynamic-variables) and [Squads](/squads). This page is retained for legacy reference.
+</Warning>
 
 Workflows is a new way to build conversational AI. It allows you to break down AI conversations into discrete steps, and then orchestrate those steps in a way that is easy to manage and modify.
 
 ## Creating Your First Workflow
 
+<Warning>
+The steps below are retained for legacy reference only. **Don't create new workflows** — the dashboard still allows it, but new builds should use [Assistants](/assistants/dynamic-variables) or [Squads](/squads) instead.
+</Warning>
+
 Begin by creating an assistant on the Assistants page and providing the required information, such as the assistant's name and capabilities. Once your assistant is set up, switch the model provider to Vapi and click "Create Workflow" when prompted. A modal will appear offering you the option to create a new workflow or attach to an existing one. Choose the appropriate option to proceed to the Workflow Builder.
 
 <Steps>

diff --git a/fern/workflows/examples/appointment-scheduling.mdx b/fern/workflows/examples/appointment-scheduling.mdx
@@ -6,6 +6,8 @@ description: Build a voice AI appointment scheduling workflow with calendar inte
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use **Assistants** or **Squads**. See the updated guides: [Assistant - Appointment Scheduling](/assistants/examples/appointment-scheduling) or [Squads](/squads).
 </Warning>
 

diff --git a/fern/workflows/examples/clinic-triage-scheduling.mdx b/fern/workflows/examples/clinic-triage-scheduling.mdx
@@ -6,6 +6,8 @@ description: Build a voice AI clinic workflow with medical triage protocols, app
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use **Squads** for multi-assistant triage and scheduling. See: [Squad - Clinic Triage & Scheduling](/squads/examples/clinic-triage-scheduling).
 </Warning>
 

diff --git a/fern/workflows/examples/ecommerce-order-management.mdx b/fern/workflows/examples/ecommerce-order-management.mdx
@@ -6,6 +6,8 @@ description: Build a voice AI e-commerce workflow with order tracking, return pr
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use **Squads** with specialized assistants for orders, returns, and VIP support. See: [Squad - E‑commerce Order Management](/squads/examples/ecommerce-order-management).
 </Warning>
 

diff --git a/fern/workflows/examples/lead-qualification.mdx b/fern/workflows/examples/lead-qualification.mdx
@@ -6,6 +6,8 @@ description: Build a voice AI outbound sales workflow with lead qualification, C
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use **Assistants** or **Squads**. See: [Assistant - Lead Qualification](/assistants/examples/lead-qualification) and [Squads](/squads).
 </Warning>
 

diff --git a/fern/workflows/examples/multilingual-support.mdx b/fern/workflows/examples/multilingual-support.mdx
@@ -6,6 +6,8 @@ description: Build a multilingual voice AI customer support workflow with langua
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use a **Squad** with language‑specific assistants. See: [Squad - Multilingual Support](/squads/examples/multilingual-support).
 </Warning>
 

diff --git a/fern/workflows/examples/property-management.mdx b/fern/workflows/examples/property-management.mdx
@@ -10,6 +10,8 @@ description: Build a voice AI property management system with dynamic call routi
 </Frame>
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 This example uses Workflows. For new builds, use **Squads** with a router assistant and domain specialists. See: [Squad - Property Management Routing](/squads/examples/property-management).
 </Warning>
 

diff --git a/fern/workflows/overview.mdx b/fern/workflows/overview.mdx
@@ -5,17 +5,9 @@ slug: workflows/overview
 ---
 
 <Warning>
-We no longer recommend Workflows for new builds. Prefer **Assistants** or **Squads** depending on complexity. See [Assistants](/assistants/dynamic-variables) and [Squads](/squads). This page is retained for legacy reference.
-
-Why We’ve Moved Away from Workflows
-
-While the Workflows product is fully built, we’ve found that current AI systems aren’t yet capable of acting as truly autonomous agents that can:
-
-1. Maintain awareness of the current node’s instructions
-2. Understand all possible next steps and the conditions required to reach them
-
-In contrast, the Squads pattern has consistently led to better results for customers. We’re now focusing on improving the ergonomics and developer experience around Squads to make this approach even more effective.
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
 
+We no longer recommend Workflows for new builds. Prefer **Assistants** or **Squads** depending on complexity. See [Assistants](/assistants/dynamic-variables) and [Squads](/squads). This page is retained for legacy reference.
 </Warning>
 
 ## Introduction

diff --git a/fern/workflows/quickstart.mdx b/fern/workflows/quickstart.mdx
@@ -6,6 +6,8 @@ description: Build a simple agent that greets users and gathers basic informatio
 ---
 
 <Warning>
+Workflows will be retired on **August 18, 2026**. From August 19, 2026 onward, existing workflows will no longer run. **Don't create new workflows** — even though the dashboard still allows it. [Migrate to Squads](/workflows/legacy-migration) before then to avoid disruption.
+
 We no longer recommend Workflows for new builds. Use **Assistants** for most cases or **Squads** for multi-assistant setups. See [Assistants](/assistants/dynamic-variables) and [Squads](/squads). Existing workflow content remains for reference.
 </Warning>