Workflows to Squads Migration

Overview

Sulus Workflows — the visual, node-and-edge conversation builder — are being retired on August 18, 2026. From that date, existing workflows will no longer run. The recommended replacement is Squads: instead of a single visual graph, you build a small set of specialized assistants that hand off to each other. This page is a dedicated reference for customers still on Workflows who need to migrate before the retirement date, mapping each Workflows concept to its Squads equivalent. For background on the two systems individually, see Workflow Builder and Squad API: Create, Update, List.

Workflows retire on August 18, 2026. If you have a live workflow in production (attached to a phone number or referenced by workflowId in a call), it will stop running on that date unless you migrate it to an Assistant (for a single-flow use case) or a Squad (for a multi-step, multi-specialist flow) beforehand. Plan the migration with enough lead time to test the new Squad thoroughly before cutting over your live phone number.

Each Workflows concept maps to a Squads equivalent as follows:

Do not assume a 1:1 mapping between nodes and Squad members. Workflows with many nodes (for example, IVR-style menus) will produce an unwieldy, hard-to-maintain Squad if you convert every node into its own assistant. Instead:

• Bundle related nodes into a small number of well-defined stages (for example: intake → triage → scheduling → human handoff)
• Create one assistant per stage, each with a focused prompt covering one to three goals at most
• Use Handoff tools to move between stages, extracting and passing variables at each boundary
• Avoid cyclical handoffs — if two stages would repeatedly hand back and forth, consolidate them into a single assistant instead; frequent back-and-forth adds latency and can introduce errors

Wherever your integration currently references a workflow (for example, a workflowId attached to a phone number, or passed when creating a call), switch that reference to your new Squad's squadId instead — or to an assistantId if a single assistant is now sufficient for what used to be a multi-node workflow. Example of what a call configuration looks like after migration:

{
  "squadId": "your-new-squad-id",
  "customer": { "number": "+1234567890" },
  "phoneNumberId": "your-phone-number-id"
}

Test the new Squad thoroughly with your saved squadId before repointing your live phone number away from the old workflowId.

1. Map your existing workflow's nodes into logical stages using the table above, rather than one assistant per node
2. Build and save each stage as an assistant, with a focused system prompt
3. Configure Handoff tools between assistants, replacing edge conditions with handoff descriptions and moving variable extraction into the Handoff tool
4. Recreate API Request Nodes and Transfer Call Nodes as tools on the relevant Squad member
5. Assemble the assistants into a Squad, with the correct first member as the entry point
6. Test the Squad end-to-end before your production cutover
7. Update your phone number or call configuration to reference the new squadId (or assistantId) instead of the old workflowId
8. Complete this before August 18, 2026, when Workflows stop running

See Workflow Builder for the legacy node/edge reference, Squads & Handoffs for how handoffs and context engineering work, Squad API: Create, Update, List for the API reference, and Squad Routing for advanced handoff destination configuration.