Webex Connect digital channel flow orchestration

Verified 2026-09-05 · 56 claims · sources tier 2–4 · 6 disputed

Also known as Connect Flow Builder, Digital Routing service, Flow Builder, Flow Canvas, Make Live, Node Runtime Authorization, QueueTask node, Voice Flow Builder, Webex Connect, Webex Engage, Working Draft.

Webex Connect serves as a communications platform as a service (CPaaS) that integrates with Webex Contact Center rather than being contained within it 44. Digital channel flow orchestration operates across these two distinct systems to handle messaging channels, routing tasks, and agent interactions 44​33.

Architecture and Provisioning

When a Webex Contact Center organisation is created, Webex Contact Center automatically provisions Webex Engage and Webex Connect as digital services while synchronising administrator accounts between the products 47. A newly added Control Hub administrator must create their Webex Connect user account and sign in within seven days; otherwise, the user account must be recreated to establish access 35. Webex Contact Center digital channels operate under controlled general availability, requiring customers to coordinate onboarding with the Cisco Solution Assurance team 22.

Before digital channel setup can begin, the Webex CC Task and Webex CC Engage node integrations in Webex Connect must be set to an Authorized state, which permits Webex Connect nodes to communicate with Webex Contact Center and Webex Engage 31. For SMS, Livechat, Facebook Messenger, and WhatsApp, the channel asset is generated directly in Webex Connect and then bound to a Webex Contact Center entry point 11. Email is the exception: its asset is created directly in Control Hub 11. Once an Email channel asset is created in Control Hub, its assigned service and Email channel cannot be changed 24.

Entry points and queues are managed in the Webex Contact Center Management Portal rather than in Webex Connect 25. The entry point uses the Social Channel channel type and links to the Webex Connect asset through the Asset Name field 25.

WarmTransfer's reading of the sources is that Webex Contact Center's Flow Designer and Webex Connect's Flow Builder are separate applications featuring independent sign-ins, separate tenants, and different node vocabularies; they are easily conflated because both environments employ the terms flow, node, and voice, and Webex Connect includes voice and interactive-voice-response nodes within its own builder 41. Webex Connect previously included a separate Voice Flow Builder for IVR workflows, but that builder has been deprecated in favor of using voice nodes directly inside the main Flow Builder 43.

Flow Builder Mechanics and Templates

In Webex Connect, a flow represents the logic for a single communication use case on an authoring canvas made up of nodes—reusable blocks that send messages, execute HTTP requests, or evaluate logic conditions 26. The overall palette covers generic messaging nodes (SMS, Email, Push, MMS, WhatsApp, Messenger, Live Chat, Apple Messages for Business, and RCS), logic and data nodes, bot and AI nodes, and a voice node group (Call Workflow, Call User, Collect Input, Play, Record, Call Patch, IVR Menu, and Call Transfer) 21.

Branching in Webex Connect is modeled using node outcomes rather than separate error-path objects; each node provides two or more outcomes, and at least one outcome must connect to a subsequent node for execution to proceed 32. Flows exist in two states: Working Draft (which is saved, allows configuration errors, and does not handle live traffic) and Live (which is published and processes incoming triggers) 46. Clicking Save creates a Working Draft, clicking Make Live publishes it, and an active flow can subsequently be paused from the flow listing page 46. Flow runs initiated prior to a new version's publication continue executing against the version that was live when they began; only newly triggered runs run the updated flow 28. Flow version comments are limited to a maximum of 250 characters 42. The maximum allowed size of a flow is 10 MB, and Cisco recommends keeping flow sizes beneath that threshold to prevent save or publication errors 29.

Predefined flow templates for digital channels are hosted in the Cisco DevNet GitHub repository rather than packaged inside Webex Connect, and administrators import them by selecting Create Flow and then Upload a Flow 40. Every pre-built Webex Contact Center node within an imported template must be opened individually and configured using Node Runtime Authorization, as node authorization is applied per node rather than tenant-wide 23. This is disputed: Cisco's sample-templates documentation states that a total of seven representative flows are available while the table immediately below it lists eight named flows 34.

Cloud Digital Channel Orchestration

Cloud Webex Contact Center documents six supported digital channels: Facebook Messenger, Livechat, Email, SMS, Apple Messages for Business, and WhatsApp 36. For task integration on cloud deployments, documentation specifies nine Webex CC Task nodes: Create Task, Set Variable, Queue Task, PIQ and EWT, Routed Notification, Modify Notification, Screen Pop, Close Task, and Resolve Conversation 30.

For digital interactions, skill requirements and contact priorities are assigned directly on the QueueTask node in the Webex Connect flow 39. Webex Contact Center defines four skill types for digital skills-based routing: proficiency (a value from 0 to 10 representing expertise), boolean (true or false), text (matched exactly), and enum (a named set of predefined values) 27.

If an eligible agent is not matched within the time defined on the QueueTask node, skill relaxation settings configured on that node can decrement or remove required skills 38. This is disputed: Cisco states that Webex Contact Center does not currently support assigning a skill profile to a team, only to an individual agent 37.

When a queued task routes to an agent, Webex Connect processes a Task Routed trigger in a dedicated global Routed flow 33. An Add Participant to Conversation node adds the agent so the interaction appears in the Agent Desktop, and an optional Screen Pop node can present a URL to that agent 33.

All inbound and outbound digital attachments are scanned for malware; any file failing this scan is dropped in both directions and displayed in Agent Desktop as an unknown or blocked file with download capabilities removed 12. Specific channels carry functional constraints: WhatsApp does not support message templates (despite the template option appearing in the compose UI), multi-format styling, customer-facing real-time read receipts, deletion synchronization when messages are deleted for everyone, voice messages, or WhatsApp Payments 45. This is disputed: the cloud Webex Contact Center article documents four Apple Messages for Business rich message types: List Picker, Time Picker, Forms, and Rich Links 10.

Contact Center Enterprise Integration

A Contact Center Enterprise (CCE) deployment integrated with Webex Connect cannot share a Webex Connect instance or Control Hub organization with a cloud Webex Contact Center deployment that has digital channels active 13. Cisco directs partners to create a distinct Control Hub organization using a different administrator email address as a temporary workaround 13. CCE integration requires release 12.6(2) or higher across the CCE router, logger, administration workstation, peripheral gateway, Cisco Finesse, Cisco IdS, and Cloud Connect 19.

The node set for CCE integrations is limited to three nodes: Create Task, Get Task Details, and End Task 17. No Queue Task node is provided for CCE 17. We infer that task queuing and agent skill matching for CCE digital tasks take place within CCE's own precision queues and skill groups rather than inside Webex Connect flows 18.

CCE integration with Webex Connect governs distinct task and message lifecycles across several operational areas 20​15​16​14:

• Transfers: During a task transfer, the Digital Routing service issues a TRANSFERRED webhook and allows up to 15 seconds for Webex Connect to present a new create-task request with the matching task ID; if not received within 15 seconds, the task terminates under the CD_TASK_TRANSFER_TIMEOUT disposition code 20.
• Task Memory: Completed tasks persist in the Digital Routing service's memory for only 15 minutes and are not stored permanently there 15. Administrators cannot alter this duration, and historical reporting must be retrieved from the Route Call Detail and Termination Call Detail database tables 15.
• Disposition Branching: The Close Task webhook delivers disposition codes indicating task completion reasons (normal completion, transfer, task lifetime expiration, customer abandon, or specific errors), which flow designers can use to branch flows and send corresponding customer messages 16.
• Attachments: Anti-malware and PCI scanning services enforce a general attachment ceiling of 25 MB or less per file; larger files are withheld from agents 14. Apple Messages for Business is exempt from this limit, permitting files up to 100 MB to comply with Apple messaging provider standards before rejecting files 8.
• Apple Messages for Business Elements: This is disputed: the Contact Center Enterprise article documents five Apple Messages for Business rich message types, the four in the cloud article plus Quick Replies, which lets agents send a pre-written question with response options 9.

Applicability

The behaviors and configurations described in this article apply to Cisco Webex Connect and its integrations with Webex Contact Center (cloud deployment) and Contact Center Enterprise (CCE) 44​13. Contact Center Enterprise environments require component versions 12.6(2) or higher 19. All cited features reflect system rules and platform releases current as of 2026-09-04 44.

What remains uncertain

The exact discrepancy regarding whether sample templates total seven or eight items is not covered by any claim in this article beyond the documented documentation contradiction; this is disputed 34. Furthermore, whether Quick Replies for Apple Messages for Business can be rendered in cloud Webex Contact Center deployments is not covered by any claim in this article, as sources disagree on rich message type coverage across deployment documents 10​9. Support for assigning skill profiles directly to teams is not covered by any claim in this article beyond the documented limitation; this is disputed 37.

WarmTransfer. (2026, September 5). Webex Connect digital channel flow orchestration. WarmTransfer. https://warmtransfer.net/knowledge/webex-connect-digital-flows

@misc{warmtransfer-webex-connect-digital-flows,
  title  = {Webex Connect digital channel flow orchestration},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-connect-digital-flows},
  note   = {Verified 2026-09-05}
}