# Webex Contact Center integration connectors Canonical: https://warmtransfer.net/knowledge/wxcc-integration-connectors Last verified: 2026-09-05 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](https://warmtransfer.net/knowledge/wxcc-connector-types). - See also [The Microsoft Dynamics 365 and Microsoft Teams connector entries](https://warmtransfer.net/knowledge/wxcc-connector-dynamics-and-teams). - See also [Webex Contact Center platform generations and predecessors](https://warmtransfer.net/knowledge/webex-cc-platform-generations). - See also [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer). - See also [The Flow Designer virtual agent activities](https://warmtransfer.net/knowledge/wxcc-virtual-agent-activities). - See also [Which Flow Designer activities can send customer data outside the platform](https://warmtransfer.net/knowledge/wxcc-flow-data-egress). ## Applicability Applies to: Cisco Webex Contact Center. Sources checked 2026-09-05. 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 the sources below. - What fields a connector record holds and where underlying credentials are stored are not covered by the sources below. - Whether a flow author can enumerate connectors they are not entitled to use is not covered by the sources below. - How long a deactivated connector keeps working for running scripts is not covered by the sources below. ## Sources [^1]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Edit a Connector, deactivated-connector options. Checked 2026-09-05. [^2]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Configure a Connector, whole section. Checked 2026-09-05. [^3]: The connector identifier cannot be modified after creation. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Edit a Connector, deactivated-connector options. Checked 2026-09-05. [^4]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Edit a Connector, steps 2 and 3. Checked 2026-09-05. [^5]: The article states that the earlier Webex Contact Center 1.0 platform supports 2 connector types, Salesforce and Custom. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Availability of connectors. Checked 2026-09-05. [^6]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Edit a Connector, step 2 and the deactivated-connector options. Checked 2026-09-05. [^7]: A connector governs credentials rather than destinations: the Flow Designer article describes a connector as a common location to store credentials, and the same activity lets a flow author turn off the authenticated-endpoint toggle and type a destination URL directly (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), HTTP Request, Connector field and Use Authenticated Endpoint toggle. Checked 2026-09-05. [^8]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Whole article; against the Flow Designer HTTP Request section. Checked 2026-09-05. [^9]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Whole article. Checked 2026-09-05. [^10]: Flow Designer states that only active connectors appear in the connector drop-down of the text-to-speech activities. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Collect Digits, Menu and Play Message, Connector field. Checked 2026-09-05. [^11]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Edit a Connector; whole article. Checked 2026-09-05. [^12]: Cisco describes the Salesforce connector as essentially creating the domain section of the URL for an HTTP Request. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), HTTP Request, Connector field description. Checked 2026-09-05. [^13]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Availability of connectors; Configure a Connector; Related Articles. Checked 2026-09-05. [^14]: 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. Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Availability of connectors; Configure a Connector; Related Articles. Checked 2026-09-05. [^15]: Cisco names a Webex Contact Center credential service, described as part of the Control Hub connector, which keeps the OAuth access token valid so that flow developers do not manage refresh. Source: [Configure custom connector for Webex Contact Center](https://help.webex.com/en-us/article/n4u702ab/Configure-custom-connector-for-Webex-Contact-Center), Configure custom connector, password grant material. Checked 2026-09-05. [^16]: A custom connector record holds a name, an authentication type and a resource domain URL, and carries up to 2 secrets in one record depending on the grant chosen: a private key or certificate, a client secret, or a password. Source: [Configure custom connector for Webex Contact Center](https://help.webex.com/en-us/article/n4u702ab/Configure-custom-connector-for-Webex-Contact-Center), Configure custom connector, authentication and grant fields. Checked 2026-09-05. [^17]: The connector overview links to the Microsoft Dynamics 365 article through an authoring preview address rather than a published one (field report). Source: [Set up integration connectors for Webex Contact Center](https://help.webex.com/en-us/article/7fuy63/Set-Up-Integration-Connectors-for-Webex-Contact-Center), Related Articles list, Microsoft Dynamics 365 entry. Checked 2026-09-05. [^18]: A Google Contact Center AI connector record holds a name, a project name, a billable project name and a billable service account, and the administrator types no secret; authentication is a Google sign-in. Source: [Configure Google CCAI connector](https://help.webex.com/en-us/article/9zvadfb/Configure-Google-CCAI-connector), Configure Google CCAI connector, record fields. Checked 2026-09-05. [^19]: The Google Contact Center AI connector article states no maximum number of connectors of this type. Source: [Configure Google CCAI connector](https://help.webex.com/en-us/article/9zvadfb/Configure-Google-CCAI-connector), Configure Google CCAI connector, record fields. Checked 2026-09-05. [^20]: The HTTP connector article is the only one of the 5 per-type articles that publishes a role matrix, naming 6 roles with read and write access, 3 with no access and 1 with read-only access. Source: [Create Webex Contact Center HTTP connector](https://help.webex.com/en-us/article/n54f5wd/Create-Webex-Contact-Center-HTTP-connector), Create Webex Contact Center HTTP connector, role table. Checked 2026-09-05. [^21]: None of the 5 per-type connector articles states where a credential is stored, in what form, whether it is encrypted, or whether it can be read back. Source: [Configure custom connector for Webex Contact Center](https://help.webex.com/en-us/article/n4u702ab/Configure-custom-connector-for-Webex-Contact-Center), All 5 per-type articles read in full; the overview's Credentials section named and never described. Checked 2026-09-05.