# Building reusable subflows in Webex Contact Center Flow Designer

Systems: Webex Contact Center

For Contact Center administrators and flow developers who already build and publish main flows in Flow Designer and want to move repeated logic into subflows.

Canonical: https://warmtransfer.net/guides/wxcc-subflow-setup

Last verified: 2026-10-01

Cisco says subflows can use the same integration interfaces as main flows, and the Subflow activity passes inputs into a subflow and returns outputs to the main flow[^37][^1]. Cisco gives business hours checks, common queue treatments and common HTTPS API calls to external services as examples of logic suited to subflows[^46].

## Before you start

- Accessing Flow Designer requires a Premium Agent License plus a user profile with rights to edit flows[^47].
- Webex Contact Center access settings give each resource type one of 3 levels: No Access, View, or Edit, and Edit also allows creating new resources[^48].
- A resource collection assigned through a user profile limits which resources an administrator can reference, so a user limited to 2 queues can build flows only with those queues[^49].
- Flows are managed in Control Hub under Contact Center > Customer Experience > Flows, then Manage Flows[^50].
- Inventory the global variables your main flows use; global variables are created by an administrator in the Provisioning module of Control Hub, and flow developers consume them inside a flow rather than fully redefining them[^51].
- Inventory the entry points that run each main flow; in a channel's entry point settings, the Routing flow drop-down selects the flow and a separate Version label field selects which version of that flow the entry point uses[^52][^53].

See also [Building a first Webex Contact Center flow](https://warmtransfer.net/knowledge/wxcc-first-flow-setup).
See also [Managing flow versions and labels and promotion in Webex Contact Center](https://warmtransfer.net/knowledge/wxcc-flow-version-label-setup).
See also [Error path behaviour across Flow Designer activities](https://warmtransfer.net/knowledge/webex-cc-flow-error-paths).

## What changes by situation

- How do you promote main flow changes to production? Dev, Test and Live version labels mapped to entry points; Latest label only.
- When you change the subflow, should every consuming flow pick the change up automatically? Cascade the change to all parent flows; Keep the change from reaching every consuming flow.
- Does the subflow need values the main flow holds in global variables, such as caller language or voice? Yes, it needs main-flow global values; No, it needs only ordinary inputs or values it computes.

## Step 1: Choose which repeated logic becomes a subflow

### Do
- Look first at the logic Cisco names as subflow material: business hours checks, common queue treatments and common HTTPS API calls to external services[^46].
- Check whether a shipped template already covers it; the Flow Designer article documents subflow templates for collecting callback information, error handling, HTTP data dip, queue treatment and scheduled callback[^43].
- Define each candidate's boundary as a list of inputs and outputs, because the Subflow activity passes inputs into the subflow and returns outputs to the main flow[^1].
- Subflows can use HTTP requests, digit collection and screen pops, which Cisco names as integration interfaces shared with main flows[^37].

### Verify
- Suggested check: each candidate has a short written list of the values it needs and the values it returns.

## Step 2: Check the candidate against documented limits

### Do
- The System limits article updated 2026-08-18 lists no subflow count limit, and its only Flow Designer content is the self-loop limits table[^24].
- A flow can contain a maximum of 30 variables in total, counting all global variables plus flow (custom) variables[^54].
- A flow can contain a maximum of 5 JSON-type variables, and a JSON-type variable's value can be up to 16 KB[^55][^56].
- If the candidate loops, Flow Designer enforces self-loop limits per activity, including 100 for Queue Contact, 1,500 for Advanced Queue Information and 750 for Escalate Call Distribution Group[^57].
- Flow-control activities are not covered by the fixed self-loop table and are instead subject to system-configured surge limits[^58].
- If you rely on Flow Analytics, note that it tracks that a subflow was added to a main flow but excludes the subflow's own internal activity data[^59].

### Verify
- Suggested check: count the inputs, outputs and working variables each candidate needs and confirm the total, together with any global values, stays within the variable limit above.

## Step 3: Create the subflow

### Do
- A Cisco tech note creates a subflow from the Subflows list by choosing Create Subflows, then Start Fresh, then entering a name[^39].
- To start from a template instead, choose one of the subflow templates for callback information, error handling, HTTP data dip, queue treatment or scheduled callback[^43].
- From 2026-04-27 Flow Designer moves to a modernized canvas with a refreshed user experience[^27].
- Flow Designer automatically saves flows to avoid data loss, autosave can be enabled or disabled, and an unpublished draft can be saved and resumed later[^60][^61].

### Verify
- Suggested check: the new subflow appears in the subflows list under the name you entered.

### Rollback
- The Flow Designer help article has a separate procedure to delete a flow[^62].
- Suggested rollback: delete the new subflow before any main flow uses it.

## Step 4: Define the subflow's inputs and outputs

**Yes, it needs main-flow global values**

### Do
- Global variables cannot be added directly in a subflow, and a global variable from the main flow can only be mapped to a local variable in the subflow[^12].
- WarmTransfer's reading of the sources is that any main-flow global value a subflow needs, such as caller language or voice, must be passed across the boundary as a mapped input to a subflow local variable[^15].
- A Cisco tech note says the global variables Global_Language and Global_VoiceName are not available inside a subflow[^40].
- The tech note's workaround is to create 2 local variables named Global_Language and Global_VoiceName in the subflow and set them with Set Variable before TTS prompts[^41].
- Define the values the subflow returns as outputs, since the Subflow activity returns outputs to the main flow[^1].
- Global variables cannot be marked as secure, so mark sensitive values on custom flow variables, which can be marked Secure to prevent logging or storage and to mask them in the Flow Debugging pane[^63][^64].

### Verify
- Suggested check: each needed global value has a matching local variable in the subflow that receives it as an input, and each return value has a variable exposed as an output.

### Rollback
- Suggested rollback: remove or rename the local variables in the draft before publishing.

**No, it needs only ordinary inputs or values it computes**

### Do
- A Webex developer blog describes 5 categories of flow data: Local (custom flow) Variables, Global Variables, Caller Associated Data (CAD) Variables, Activity Output Variables, and Event Output Variables[^65].
- Define the values the subflow receives as inputs and the values it returns as outputs, because the Subflow activity passes inputs in and returns outputs to the main flow[^1].
- Flow variables can be marked Secure, which prevents the system from logging or storing sensitive values and masks them in the Flow Debugging pane[^64].

### Verify
- Suggested check: the subflow's inputs and outputs match the boundary you wrote down in Step 1.

### Rollback
- Suggested rollback: remove the variables in the draft before publishing.

## Step 5: Build the logic and wire every error path

### Do
- Build the activities, using HTTP requests, digit collection and screen pops where needed, which Cisco says subflows can use as main flows do[^37].
- Connect each activity's Undefined Error output to a handled path; Flow Designer activities offer this error-handling path for system errors that occur during flow execution[^45].
- The Undefined Error node is not present on 4 Flow Control activities: Start Flow, End Flow, HTTP Request, and Parse[^66].
- If a flow developer does not configure an error handling path for an activity, execution falls back to the path defined in the OnGlobalError event handler[^67].
- For queue or API failures, Cisco's Error Handling Subflow handles error conditions such as problems with queue handling or API requests[^8].
- Field reports suggest that the activity set uses at least 5 different label conventions for the same idea of an outcome, such as Success and Failure on one activity and onSuccess and onError on another[^68].
- From 2026-04-24 connecting an End activity to a port is a recommendation rather than mandatory[^6].
- Flow Designer undo and redo covers the last 10 canvas actions[^69].

### Verify
- Flow validation only checks for structural errors and cannot confirm that variables resolve to expected values at runtime[^70].
- Suggested check: no activity that has an error output is left with it unconnected, and the subflow sets its outputs on both the success path and the error path so the caller can tell them apart.

### Rollback
- Undo and redo reach back only 10 canvas actions[^69].
- Suggested rollback: discard the draft changes and rebuild from the last saved state.

## Step 6: Validate and publish the subflow

### Do
- A flow must be validated and its errors fixed before it can be published[^71].
- The Publish flow button is disabled while the Validation toggle is off or any active errors exist[^72].
- In Cisco's 2026 lab, the Validation toggle is in the bottom right of the Flow Designer window, and Publish Flow sits next to it once validation reports no flow errors[^73].
- Publish the subflow, because a published subflow appears as an activity that can be placed on a main flow canvas[^38].

### Verify
- Suggested check: open a main flow draft and confirm the new subflow is offered as an activity you can place on the canvas.

### Rollback
- Flow Designer has no version control feature; the version number counts how many times the flow has been published[^74].
- Flow Designer lets a flow developer revert a flow to a previously published version[^75].

## Step 7: Choose how subflow changes propagate

**Cascade the change to all parent flows**

### Do
- Keep the subflow setting named Propagate changes to all flows enabled, which cascades a subflow change to all parent flows that consume it[^32].

### Verify
- The tech note verifies a subflow change by placing a call that passes through the subflow and listening for the expected result[^42].
- Suggested check: after a later subflow change, place a test call through every consuming main flow and confirm each one shows the new behaviour.

### Rollback
- Suggested rollback: disable the propagation setting and follow the pinned branch of this step.

**Keep the change from reaching every consuming flow**

### Do
- Disable Propagate changes to all flows before editing the subflow, which keeps the change from automatically disrupting every parent flow that consumes it[^33][^76].

### Verify
- Suggested check: after a later subflow change, confirm by test call that a consuming main flow you have not touched keeps its previous behaviour.

### Rollback
- Suggested rollback: re-enable the propagation setting and follow the cascade branch of this step.

## Step 8: Call the subflow from the main flow and map variables

### Do
- Open the main flow and place the subflow's activity on the canvas, where a published subflow appears as an activity[^38].
- Map main-flow values to the subflow's inputs and its outputs back to main-flow variables, since the Subflow activity passes inputs in and returns outputs[^1].
- A global variable from the main flow can only be mapped to a local variable in the subflow[^12].
- Connect the activity's exits, including any Undefined Error path, to handled paths[^45].

### Verify
- Validation checks only structural errors such as required fields, not runtime values[^70].
- Suggested check: every input has a mapped source, every output has a destination, and validation reports no errors.

### Rollback
- An unpublished draft can be saved and resumed later[^61].
- Suggested rollback: remove the subflow's activity from the main flow draft before publishing.

## Step 9: Publish the main flow and test end to end

**Dev, Test and Live version labels mapped to entry points**

### Do
- Validate the main flow and fix its errors, which is required before publishing[^71].
- When publishing, attach the Dev label; you can attach 1 or more version labels such as Live, Test or Dev, and Latest is applied by default and cannot be removed from the most recently published version[^77].
- Cisco's Flow Designer blog describes publishing new work with the Dev label and attaching that Dev version to a test entry point so production calls are not affected[^78].
- In Cisco's 2026 lab, an administrator binds a flow by finding the channel under Channels, setting Routing flow and Version label in its Entry Point settings section, and clicking Save[^79].
- The blog says the version label in use is chosen at the entry point and applies to every contact arriving on that entry point[^80].
- In 2026-04 the NewPhoneContact start activity is renamed NewContact as an omnichannel start node[^28].
- Place a call that passes through the subflow, as the tech note does to verify a subflow change[^42].
- The Flow Designer help article includes a section titled Debug flows[^3].

### Verify
- The Cisco lab tests a new flow by signing an agent in to the Desktop, setting the agent Available, calling the support number and checking that the call is offered to the agent[^81].
- Suggested check: the test call follows the subflow path, its outputs drive the expected main-flow branch, and calls on the production entry points behave as before.

### Rollback
- Flow Designer lets a flow developer revert a flow to a previously published version[^75].
- Suggested rollback: set the test entry point back to the version label it used before this step.

**Latest label only**

### Do
- Validate the main flow and fix its errors, which is required before publishing[^71].
- Publish it; Latest is applied by default and cannot be removed from the most recently published version[^77].
- An entry point uses the default Latest version unless it is associated with a different version label[^82].
- The Cisco lab publishes with the Latest label and sets the channel's Version label to Latest[^83].
- In 2026-04 the NewPhoneContact start activity is renamed NewContact as an omnichannel start node[^28].
- Place a call that passes through the subflow, as the tech note does to verify a subflow change[^42].
- The Flow Designer help article includes a section titled Debug flows[^3].

### Verify
- The Cisco lab tests a new flow by signing an agent in to the Desktop, setting the agent Available, calling the support number and checking that the call is offered to the agent[^81].
- Suggested check: the test call follows the subflow path and its outputs drive the expected branch, keeping in mind that entry points on the newest version now run this change.

### Rollback
- Flow Designer lets a flow developer revert a flow to a previously published version[^75].
- Suggested rollback: revert the main flow to its previous version and place a test call to confirm the old behaviour is back.

## Step 10: Promote a later subflow change with the flows that call it

**Dev, Test and Live version labels mapped to entry points**

### Do
- Cisco describes the Dev label for development, Test for staging validation and Live for production[^5].
- Publish each consuming main flow's new work with the Dev label on a test entry point, as Cisco's blog describes[^78].
- Promote a tested flow to staging by applying the Test version label[^84].
- Promote it to production by assigning the Live version label[^85].
- Cisco positions flow version labels as enabling a pipeline-driven promotion process from development to production, including blue-green deployments of flows[^2].
- To script promotion, the Flow V2 APIs let teams search, validate, publish, export, lock and unlock flows, subflows and functions[^86].

### Verify
- The tech note confirms a subflow change by placing a call that passes through the subflow[^42].
- Suggested check: place a test call on the entry point for each label stage and confirm the behaviour matches the version promoted to that stage.

### Rollback
- Cisco's blog presents flow versioning as enabling blue-green deployments with rollback to previous versions without downtime[^87].
- Suggested rollback: move the Live label on each consuming main flow back to its prior version.

**Latest label only**

### Do
- Each newly published flow version carries the Latest label by default, and it cannot be removed from the most recently published version[^77].
- An entry point uses the default Latest version unless it is associated with a different version label[^82].
- If you want a staging step before changing a subflow that many flows share, Cisco describes Dev for development, Test for staging validation and Live for production[^5].
- The Flow V2 APIs let teams publish and export subflows as well as flows[^86].

### Verify
- The tech note confirms a subflow change by placing a call that passes through the subflow[^42].
- Suggested check: place a test call through each consuming main flow after the change.

### Rollback
- Flow Designer has no version control feature beyond publish counts and version labels[^74].
- Flow Designer lets a flow developer revert a flow to a previously published version[^75].

## Step 11: Watch for runtime errors

### Do
- Subscribe a receiver to the flow:error webhook, which from 2026-06-25 sends observability events when a flow encounters an error[^9].

### Verify
- Suggested check: force a handled error during a test call and confirm the event arrives at your receiver.

### Rollback
- Suggested rollback: remove the webhook subscription.

## Step 12: Retire a subflow

### Do
- Export the subflow first if you may need it again; the Flow V2 APIs can export flows, subflows and functions[^86].
- Follow the Flow Designer help article's delete procedure, which it documents separately from copy, export and import[^62].

### Verify
- Suggested check: confirm no main flow still places the subflow on its canvas, then confirm the delete succeeds and the subflow is gone from the list.

### Rollback
- The Flow Designer help article has a separate procedure to import a flow[^62].
- Suggested rollback: import the exported copy and republish it.

## Applicability

Applies to: Cisco Webex Contact Center. Deployments: cloud and multi-tenant. Sources checked 2026-10-01. - From 2026-04-27 Flow Designer moves to a modernized canvas, so UI labels in older material may predate it[^27].
- In 2026-04 the NewPhoneContact start activity is renamed NewContact[^28].
- The flow:error webhook applies from 2026-06-25[^9].
- The public Flow schema and Flow V2 APIs apply from 2026-07-29[^11].
- When version labels were introduced, flows that already existed were marked with the Live version label[^88].
- Digital channel flows are built in Webex Connect rather than in Flow Designer, so they fall outside this guide[^89].

## What remains uncertain

- The exact UI labels for marking subflow variables as inputs or outputs are not covered by the sources below.
- Whether version labels can be attached to a subflow itself, and how a main flow chooses which subflow version it runs, is not covered by the sources below.
- Whether an unhandled error inside a subflow surfaces on the calling Subflow activity's error exit or ends the contact is not covered by the sources below.
- How the propagation setting interacts with republishing the consuming main flow is not covered by the sources below.
- Whether the debugging tooling shows the steps inside a subflow is not covered by the sources below.
- Whether a subflow can call another subflow, or be bound directly to an entry point, is not covered by the sources below.
- Whether the variable limits apply to a subflow separately from its main flow is not covered by the sources below.
- What happens when you delete a subflow that published main flows still use is not covered by the sources below.

## Sources

[^1]: The Subflow activity passes inputs into the subflow and returns outputs to the main flow, so passed data can change the subflow's behaviour. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), Subflows. Checked 2026-10-01.
[^2]: Cisco positions flow version labels as enabling a pipeline-driven promotion process from development to production, including blue-green deployments of flows. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Flow Versioning – Streamlining Development and Deployment. Checked 2026-10-01.
[^3]: The Flow Designer help article includes a section titled Debug flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Table of contents: Debug flows. Checked 2026-10-01.
[^4]: A subflow used by any published main flow cannot be deleted, whether or not that main flow is live or attached to an entry point; it must first be removed from the main flow or the main flow deleted. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows > Delete a subflow. Checked 2026-10-01.
[^5]: Cisco describes the Dev label for development, Test for staging validation and Live for production. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Flow Versioning – Streamlining Development and Deployment. Checked 2026-10-01.
[^6]: From 2026-04-24 connecting an End activity to a port is a recommendation rather than mandatory, which reduces validation errors when publishing. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), Entry dated April 24, 2026: Flow Designer Omnichannel Start Node and End Node Enhancements. Checked 2026-10-01.
[^7]: The Error Handling Subflow article delivers its details as an embedded PDF rather than page text. Source: [Error Handling Subflow](https://help.webex.com/en-us/article/nj4bw19), Article body (embedded PDF viewer). Checked 2026-10-01.
[^8]: Cisco's Error Handling Subflow handles error conditions in the contact center process, such as problems with queue handling or API requests. Source: [Error Handling Subflow](https://help.webex.com/en-us/article/nj4bw19), Article description. Checked 2026-10-01.
[^9]: From 2026-06-25 Flow Designer offers a flow:error webhook that sends observability events when a flow encounters an error. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), Entry dated June 25, 2026: Flow Designer error webhook for observability. Checked 2026-10-01.
[^10]: Flow List and Flow Publish APIs supplement the existing Import and Export APIs so flows and subflows can be listed, exported, imported and published between organizations programmatically. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), Entry introducing Flow List and Flow Publish APIs (date not captured). Checked 2026-10-01.
[^11]: From 2026-07-29 a public Flow schema and Flow V2 APIs let teams search, validate, publish, export, lock and unlock flows, subflows and functions programmatically. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), Entry dated July 29, 2026: Programmatic Flow Design with public Flow Schema and new APIs. Checked 2026-10-01.
[^12]: Global variables cannot be added directly in a subflow; a global variable from the main flow can only be mapped to a local variable in the subflow. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables (introduction). Checked 2026-10-01.
[^13]: The 200-subflow limit is documented in the Flow Designer article but not in the System limits article, so capacity planners who check only the limits page will miss it (inferred). Source: [System limits in Webex Contact Center](https://help.webex.com/article/n7s6ed7), Whole article. Checked 2026-10-01.
[^14]: Because a subflow cannot call another subflow, logic shared by two subflows has to be duplicated in each or moved up into the main flow (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (restrictions note). Checked 2026-10-01.
[^15]: Any main-flow global value a subflow needs, such as caller language or voice, must be passed across the boundary as a mapped input to a subflow local variable (inferred). Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables (introduction). Checked 2026-10-01.
[^16]: Because subflow changes reach a main flow only when it is republished and subflows carry their own labels, a safe promotion publishes and labels the subflow first, then republishes and relabels each consuming main flow (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows; Apply version labels to a flow. Checked 2026-10-01.
[^17]: The help article says subflow changes reach a main flow only on republish, and the 2024 blog describes a Propagate setting that cascades changes; the likely reading is that propagation controls whether consumers are republished automatically, but the sources do not say so (inferred). Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse; read with cisco-help-nhovcy4-wxcc-flow-designer Edit a subflow. Checked 2026-10-01.
[^18]: A subflow is invoked from within a flow to run logic without linking to an entry point and without leaving the main flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (introduction). Checked 2026-10-01.
[^19]: The start activity exposes a property showing which flow version label (Dev, Test, Live or Latest) is executing, so flow logic can branch on it. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), Entry on accessing Version Labels in the NewPhoneContact activity (date not captured). Checked 2026-10-01.
[^20]: Version labels let different versions of the same flow be attached to different entry points or to a GoTo activity. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Apply version labels to a flow. Checked 2026-10-01.
[^21]: A version label such as Live, Dev or Test can be attached to a subflow so the main flow can be tested end to end in the matching environment. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (version labels). Checked 2026-10-01.
[^22]: Latest is the default version label; it cannot be removed from a flow version during publishing, and other labels are applied alongside it. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Apply version labels to a flow. Checked 2026-10-01.
[^23]: Publishing a draft associates the Latest label with the new version, and only one version holds the Latest label at a time. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Apply version labels to a flow. Checked 2026-10-01.
[^24]: The System limits article updated 2026-08-18 lists no subflow count limit; its only Flow Designer content is the self-loop limits table. Source: [System limits in Webex Contact Center](https://help.webex.com/article/n7s6ed7), Whole article; Self-loop limits for Flow Designer activities. Checked 2026-10-01.
[^25]: Local variables can be passed to other flows through the GoTo activity or the Subflow activity. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow variables (local variables). Checked 2026-10-01.
[^26]: An organization can create at most 200 subflows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (introduction). Checked 2026-10-01.
[^27]: From 2026-04-27 Flow Designer moves to a modernized canvas with a refreshed user experience. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), Entry dated April 27, 2026: Modern and Unified Flow Designer Experience in Webex Contact Center. Checked 2026-10-01.
[^28]: In 2026-04 the NewPhoneContact start activity is renamed NewContact as an omnichannel start node. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), Entry dated April 24, 2026: Flow Designer Omnichannel Start Node and End Node Enhancements. Checked 2026-10-01.
[^29]: A subflow cannot be linked directly from an entry point or from a queue routing strategy. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (restrictions note). Checked 2026-10-01.
[^30]: Subflows must be invoked from main flows; a subflow cannot invoke another subflow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (restrictions note). Checked 2026-10-01.
[^31]: Subflows are created at the organization level, and a flow developer can view and invoke subflows that exist in the same organization. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (introduction). Checked 2026-10-01.
[^32]: A subflow setting named Propagate changes to all flows cascades a subflow change to all parent flows that consume it. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse. Checked 2026-10-01.
[^33]: Disabling Propagate changes to all flows when changing a subflow keeps that change from disrupting every flow that consumes the subflow. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse. Checked 2026-10-01.
[^34]: A subflow can be published independently, but changes made in the subflow take effect only after the main flow is republished. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows > Edit a subflow. Checked 2026-10-01.
[^35]: Flow Designer lets developers break large flows into smaller subflows that can be reused across multiple flows to handle specific tasks, reducing the complexity of building large flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (introduction). Checked 2026-10-01.
[^36]: A subflow can be reused multiple times within one main flow and across main flows in the organization. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (introduction). Checked 2026-10-01.
[^37]: Cisco says subflows can use the same integration interfaces as main flows, naming HTTP requests, digit collection and screen pops. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), Subflows. Checked 2026-10-01.
[^38]: A published subflow appears as an activity that can be placed on a main flow canvas. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse. Checked 2026-10-01.
[^39]: The tech note creates a subflow from the Subflows list by choosing Create Subflows, then Start Fresh, then entering a name. Source: [Configure Different Supported Languages and Voice Names with Native Text-To-Speech inside WxCC SubFlow](https://www.cisco.com/c/en/us/support/docs/contact-center/webex-contact-center/222681-configure-different-supported-languages.html), Configure. Checked 2026-10-01.
[^40]: A Cisco tech note says the global variables Global_Language and Global_VoiceName are not available inside a subflow. Source: [Configure Different Supported Languages and Voice Names with Native Text-To-Speech inside WxCC SubFlow](https://www.cisco.com/c/en/us/support/docs/contact-center/webex-contact-center/222681-configure-different-supported-languages.html), Configure. Checked 2026-10-01.
[^41]: The tech note's workaround is to create two local variables named Global_Language and Global_VoiceName in the subflow and set them with Set Variable before TTS prompts. Source: [Configure Different Supported Languages and Voice Names with Native Text-To-Speech inside WxCC SubFlow](https://www.cisco.com/c/en/us/support/docs/contact-center/webex-contact-center/222681-configure-different-supported-languages.html), Configure. Checked 2026-10-01.
[^42]: The tech note verifies a subflow change by placing a call that passes through the subflow and listening for the expected language and voice. Source: [Configure Different Supported Languages and Voice Names with Native Text-To-Speech inside WxCC SubFlow](https://www.cisco.com/c/en/us/support/docs/contact-center/webex-contact-center/222681-configure-different-supported-languages.html), Verify. Checked 2026-10-01.
[^43]: The Flow Designer article documents subflow templates for collecting callback information, error handling, HTTP data dip, queue treatment and scheduled callback. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Table of contents: Use subflow templates. Checked 2026-10-01.
[^44]: If a subflow plays text-to-speech, the audio plays in English by default unless the subflow defines a variable named like Global_VoiceName or a subflow variable is mapped with the value from the main flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage subflows (TTS note). Checked 2026-10-01.
[^45]: Flow Designer activities offer an error-handling path called Undefined Error for system errors that occur during flow execution. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activity reference sections (Undefined Error output). Checked 2026-10-01.
[^46]: Cisco gives business hours checks, common queue treatments and common HTTPS API calls to external services as examples of logic suited to subflows. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse. Checked 2026-10-01.
[^47]: Accessing the Flow Designer application requires a Premium Agent License plus a user profile with rights to edit flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Get started / Access Flow Designer. Checked 2026-09-04.
[^48]: Webex Contact Center access settings give each resource type one of three levels: No Access, View, or Edit (which also allows creating new resources). Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), user profile access levels. Checked 2026-10-01.
[^49]: A resource collection assigned through a user profile limits which resources an administrator can reference. For example, a user limited to two queues can build flows only with those queues. Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), resource collections section. Checked 2026-10-01.
[^50]: A new flow is created in Control Hub under Contact Center > Customer Experience > Flows, then Manage Flows > Create Flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Build and manage flows with Flow Designer; Create a flow. Checked 2026-09-25.
[^51]: Global variables are created by an administrator in the Provisioning module of Control Hub, and flow developers consume (add, edit default value of, or remove) them inside a flow rather than fully redefining them. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Global variables. Checked 2026-09-04.
[^52]: In a channel's entry point settings, the Routing flow drop-down selects the flow assigned to that entry point. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), entry point settings table, 'Routing flow' row. Checked 2026-10-01.
[^53]: A separate Version label field in a channel's entry point settings selects which version of the routing flow the entry point uses. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), entry point settings table, 'Version label' row. Checked 2026-10-01.
[^54]: A flow can contain a maximum of 30 variables in total, and this count includes all global variables plus flow (custom) variables regardless of whether they are reportable or agent viewable. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Create Custom Flow Variables. Checked 2026-09-04.
[^55]: A flow can contain a maximum of 5 JSON-type variables. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Create Custom Flow Variables. Checked 2026-09-04.
[^56]: A JSON-type flow variable's value can be up to 16 KB in size. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Create Custom Flow Variables. Checked 2026-09-04.
[^57]: Flow Designer enforces self-loop limits per activity: 100 for Queue Contact, 1,500 for Advanced Queue Information and 750 for Escalate Call Distribution Group. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), Flow Designer self-loop limits table. Checked 2026-09-30.
[^58]: Flow-control activities (as opposed to call-handling activities) are not covered by the fixed per-activity self-loop table; instead they are subject to system-configured surge limits to prevent infinite looping. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), System-enforced self-loop limits for activities. Checked 2026-09-04.
[^59]: Flow Analytics does not support subflows internally; it tracks that a subflow was added to a main flow but excludes the subflow's own internal activity data. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Analyze flows / Flow Analytics. Checked 2026-09-04.
[^60]: Flow Designer automatically saves flows to avoid data loss, and autosave can be enabled or disabled. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Enable or disable autosave'. Checked 2026-10-01.
[^61]: An administrator can save an unpublished flow draft and return to continue working on it later. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Enable or disable autosave'. Checked 2026-10-01.
[^62]: The Flow Designer help article has separate procedures to copy, export, import and delete a flow and to apply version labels to a flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), table of contents: 'Copy a flow', 'Export a flow', 'Import a flow', 'Delete a flow', 'Apply version labels to a flow'. Checked 2026-10-01.
[^63]: Global variables cannot be marked as secure; only custom flow variables can be marked secure. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Custom variables. Checked 2026-09-04.
[^64]: Flow variables can be marked Secure, which prevents the system from logging or storing sensitive values and masks those values in the Flow Debugging pane. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions / Custom variables. Checked 2026-09-04.
[^65]: A Webex developer blog describes 5 categories of flow data: Local (custom flow) Variables, Global Variables, Caller Associated Data (CAD) Variables, Activity Output Variables, and Event Output Variables. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), developer.webex.com blog / Data Definitions for Effective Flow Design. Checked 2026-09-04.
[^66]: The Undefined Error node (used to route undefined system errors) is not present on 4 Flow Control activities: Start Flow, End Flow, HTTP Request, and Parse. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Configure error handling. Checked 2026-09-04.
[^67]: If a flow developer does not configure an error handling path for an activity, execution falls back to the path defined in the OnGlobalError event handler. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Configure error handling. Checked 2026-09-04.
[^68]: The activity set uses at least 5 different label conventions for the same idea of an outcome: Success and Failure on one activity onSuccess and onError on another Handled and Escalated and Error on a third Errored on its successor and True and False on the branching activities (field report). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, activity output ports across the catalogue. Checked 2026-09-15.
[^69]: Flow Designer undo and redo covers the last 10 canvas actions. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), canvas actions, undo/redo. Checked 2026-09-30.
[^70]: Flow validation only checks for structural errors (required fields, valid structure); it cannot evaluate functions or confirm that variables resolve to expected values at runtime. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows / Validate a flow. Checked 2026-09-04.
[^71]: A flow must be validated and its errors fixed before it can be published. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Footer pane' (flow validation and publishing). Checked 2026-10-01.
[^72]: A flow cannot be published unless validation succeeds; the Publish flow button is disabled while the Validation toggle is off or any active errors exist. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows / Validate a flow, Publish a flow. Checked 2026-09-04.
[^73]: In Cisco's 2026 lab, the Validation toggle is in the bottom right of the Flow Designer window, and Publish Flow sits next to it once validation reports no flow errors. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), flow publishing steps, validation. Checked 2026-10-01.
[^74]: Flow Designer has no version control feature. The flow version number counts how many times the flow has been published, and version labels can be applied. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), flow versioning section. Checked 2026-09-30.
[^75]: Flow Designer lets a flow developer revert a flow to a previously published version. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated August 5, 2022, 'Flow Designer Enhancements'. Checked 2026-10-01.
[^76]: Subflows have a 'Propagate changes to all flows' setting; disabling it before editing a subflow prevents a change in that subflow from automatically disrupting every parent flow that consumes it. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), developer.webex.com blog / Subflows – Enhancing Modularity and Reuse. Checked 2026-09-04.
[^77]: When publishing a flow, you can attach 1 or more version labels (such as Live, Test, or Dev); 'Latest' is applied by default and cannot be removed from the most recently published version. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows / Publish a flow. Checked 2026-09-04.
[^78]: Cisco's Flow Designer blog describes publishing new work with the Dev label and attaching that Dev version to a test entry point so production calls are not affected. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Dev (Development)'. Checked 2026-10-01.
[^79]: In Cisco's 2026 lab, an administrator binds a flow by finding the channel under Channels, setting Routing flow and Version label in its Entry Point settings section, and clicking Save. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), channel configuration steps, 'Entry Point settings'. Checked 2026-10-01.
[^80]: The blog says the version label in use is chosen at the entry point and applies to every contact arriving on that entry point. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', implementation paragraph. Checked 2026-10-01.
[^81]: The Cisco lab tests a new flow by signing an agent in to the Webex Contact Center Desktop, setting the agent Available, calling the support number and checking that the welcome prompt plays and the call is offered to the agent. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), Mission 1; testing step. Checked 2026-09-25.
[^82]: Flow version labels can be associated with entry point mappings, so an entry point can use a labelled version instead of the default Latest version. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01.
[^83]: The Cisco lab publishes the flow with the Latest label, then on the channel sets Routing flow to that flow, Music on hold to defaultmusic_on_hold.wav and Version label to Latest, and saves. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), Mission 1; flow publishing and channel mapping steps. Checked 2026-09-25.
[^84]: The blog's next stage promotes a tested flow to the Test (staging) environment by applying the Test version label. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Test (Staging)'. Checked 2026-10-01.
[^85]: The blog's final stage promotes a flow to production by assigning the Live version label. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Live (Production)'. Checked 2026-10-01.
[^86]: The Flow V2 APIs let teams search, validate, publish, export, lock and unlock flows, subflows and functions. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated July 29, 2026, 'Programmatic Flow Design with public Flow Schema and new APIs'. Checked 2026-10-01.
[^87]: Cisco's blog presents flow versioning as enabling blue-green deployments with rollback to previous versions without downtime. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', rollback and blue-green paragraph. Checked 2026-10-01.
[^88]: When version labels were introduced, flows that already existed were marked with the Live version label. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01.
[^89]: Digital channels for Webex Contact Center (Facebook Messenger, live chat, email, SMS, Apple Messages for Business, WhatsApp) are configured through Webex Connect, and their flows are built in Webex Connect rather than in Flow Designer. Source: [Set up digital channels in Webex Contact Center](https://help.webex.com/en-us/article/n954r0k/Set-up-digital-channels-in-Webex-Contact-Center), overview and setup steps (final step 'Create flows in Webex Connect'). Checked 2026-09-30.