Webex Contact Center integration connectors

Verified 2026-09-05 · 21 claims · sources tier 2

Also known as CCAI Config, Connector ID, Refresh Key.

WarmTransfer's reading of the sources is that Webex Contact Center integration connectors store authentication details that flow activities use to integrate with external systems 11​7. WarmTransfer's reading of the sources is that a connector governs credentials rather than destinations, as Flow Designer positions a connector as a common location to store credentials while permitting authors to disable authenticated endpoints and supply destination URLs directly 7.

Connector types across platform generations

The earlier Webex Contact Center 1.0 platform supports 2 connector types: Salesforce and Custom 5.

Documentation for the current platform contains 3 connector type lists that do not agree: an availability sentence listing 6 types, a configuration list containing 9 types, and a related-articles list linking to 8 entries 13. Specifically, Google is listed plain in the availability sentence but as Google TTS in the configuration list without clarifying whether they share the same connector record 14. Furthermore, ServiceNow, Microsoft Dynamics 365, and Microsoft Teams appear solely in the configuration list without inclusion in either availability sentence, and ServiceNow lacks a related-articles link altogether 14.

Configuration and lifecycle management

The section titled Configure a Connector contains only a list of connector names, omitting fields, steps, and procedures, deferring setup entirely to separate articles 2. Cisco does not state what fields a connector record holds, what format they take, or where underlying credentials reside, though an edit page provides a Credentials section 11. Furthermore, documentation names no roles, permissions, or entitlements needed to create, edit, deactivate, reactivate, or delete a connector 9. The connectors documentation also names no authentication scheme for any connector type, though Flow Designer lists Basic Auth and OAuth 2.0 for authenticated HTTP Request endpoints 8.

A connector's identifier cannot be modified after creation 3. To edit credentials, administrators must deactivate the connector first; deactivation does not immediately terminate active scripts, which may continue executing for some time while their credentials remain valid 4.

Specific connectors impose unique lifecycle constraints:

• Cisco describes the Salesforce connector as essentially creating the domain section of the URL for an HTTP Request activity 12.
• Editing or reactivating the Google Contact Center AI connector requires reauthenticating with Google, a refresh flow that must run outside business hours with browser pop-up blockers disabled 6.
• A Google Contact Center AI connector cannot be deleted while associated with a CCAI configuration, though the documentation never defines what a CCAI configuration is or where administrators manage it 1.

In Flow Designer, text-to-speech activities display only active connectors within their connector drop-down menus 10.

See also

• See also What each Webex Contact Center connector type stores.
• See also The Microsoft Dynamics 365 and Microsoft Teams connector entries.
• See also Webex Contact Center platform generations and predecessors.
• See also Webex Contact Center Flow Designer architecture.
• See also The Flow Designer virtual agent activities.
• See also Which Flow Designer activities can send customer data outside the platform.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-05. The deployment model is not covered by any claim in this article. Documentation covers the earlier Webex Contact Center 1.0 platform for its 2 supported connector types 5.

What remains uncertain

• The contents of the 8 per-connector-type articles deferred to by the overview are not covered by any claim in this article.
• What fields a connector record holds and where underlying credentials are stored are not covered by any claim in this article.
• Whether a flow author can enumerate connectors they are not entitled to use is not covered by any claim in this article.
• How long a deactivated connector keeps working for running scripts is not covered by any claim in this article.

WarmTransfer. (2026, September 5). Webex Contact Center integration connectors. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-integration-connectors

@misc{warmtransfer-wxcc-integration-connectors,
  title  = {Webex Contact Center integration connectors},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-integration-connectors},
  note   = {Verified 2026-09-05}
}