Set up integration connectors for Webex Contact Center

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center

Published

2026-07-19

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• A Google Contact Center AI connector cannot be deleted while a CCAI configuration is associated with it, and the article never defines what a CCAI configuration is or where it is managed. fact in context
• The section titled Configure a Connector contains only a list of connector names, with no fields, no steps and no procedure; per-type setup is deferred entirely to separate articles. fact in context
• The connector identifier cannot be modified after creation. fact in context
• A connector must be deactivated before its credentials can be edited, and deactivation does not immediately stop scripts already running, which may keep working for some time while their credentials remain valid. fact in context
• The article states that the earlier Webex Contact Center 1.0 platform supports 2 connector types, Salesforce and Custom. fact in context
• Editing or reactivating the Google Contact Center AI connector requires reauthenticating with Google, and the refresh flow is to be run outside business hours with the browser pop-up blocker disabled. fact in context
• The connectors article names no authentication scheme for any connector type, while the Flow Designer article names Basic Auth and OAuth 2.0 for authenticated HTTP Request endpoints. fact in context
• The article never names any role, permission or entitlement required to create, edit, deactivate, reactivate or delete a connector, and never says whether a flow author can enumerate connectors they are not entitled to use. fact in context
• The article never states what fields a connector record holds, in what form, or where the underlying credential values are stored, although it names a Credentials section on the edit page. fact in context
• The connectors article carries 3 lists of connector types that do not agree: an availability sentence naming 6 for the current platform, a configuration list naming 9, and a related-articles list of 8 links. fact in context
• In the connectors article, Google appears plain in the availability sentence but as Google TTS in the configuration list with no statement of whether they are the same connector; ServiceNow, Microsoft Dynamics 365 and Microsoft Teams appear in the configuration list but in neither availability sentence; and ServiceNow has no related-articles link at all. fact in context
• The connector overview links to the Microsoft Dynamics 365 article through an authoring preview address rather than a published one. field-pattern in context

Cite this source record

APA

WarmTransfer. (2026, July 19). Set up integration connectors for Webex Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-7fuy63-wxcc-integration-connectors

BibTeX

@misc{warmtransfer-cisco-help-7fuy63-wxcc-integration-connectors,
  title  = {Set up integration connectors for Webex Contact Center},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-7fuy63-wxcc-integration-connectors},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-05}
}