# What each Webex Contact Center connector type stores

Canonical: https://warmtransfer.net/knowledge/wxcc-connector-types

Last verified: 2026-09-05

Across Webex Contact Center, each connector type stores a specific set of configuration parameters, identifiers, and authentication credentials[^11][^8][^19][^22]. 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[^20].

## Stored fields and credential handling

WarmTransfer's reading of the sources is that of the 5 documented connector types, 2 require the administrator to type no secret at all: Google Contact Center AI, which uses a Google sign-in, and the Webex Contact Center HTTP connector, where the platform mints the identity[^21].

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 because authentication is handled via a Google sign-in[^11]. Google Contact Center AI credentials are delivered by an email whose subject is CCAI Onboarding Provision Status Update, and the Google project identifier is mapped to Cisco's service account through a hosted form[^13].

A Salesforce connector record holds a name, a client identifier that Salesforce calls a consumer key, an email address, a URL, and a private key, and carries no client secret[^19].

A Webex Experience Management connector record holds a name, a description, and the username and API key of a service account[^22].

A custom connector record holds a name, an authentication type, and a resource domain URL[^8]. It carries up to 2 secrets in one record depending on the grant chosen: a private key or certificate, a client secret, or a password[^8]. A custom connector supports Basic Auth, which is the default, or OAuth 2.0 with 3 grant types[^9]. This is disputed: the custom connector article presents a grant type field under Basic Authentication, having stated a step earlier that grant types exist only for OAuth 2.0[^7]. 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[^6].

For the Webex Contact Center HTTP connector, creating the record requires ticking a checkbox authorising the connector to read, write, modify, and delete data in the Contact Center solution[^14]. In the field, the HTTP connector article lists UPDATE among the HTTP verbs[^17].

## Connector inventory and limits

Two of the connector articles publish a per-type maximum: 10 custom connectors and 5 Salesforce connectors, with 1 Webex Experience Management connector[^18]. The Google Contact Center AI connector article states no maximum number of connectors of this type[^12].

| Connector type | Stored fields and credentials | Published limit |
| --- | --- | --- |
| Google CCAI | Name, project name, billable project name, billable service account[^11] | None stated[^12] |
| Salesforce | Name, consumer key, email, URL, private key[^19] | 5[^18] |
| Webex Experience Management | Name, description, service account username, API key[^22] | 1[^18] |
| Custom connector | Name, auth type, domain URL, up to 2 secrets[^8] | 10[^18] |
| HTTP connector | Authorization checkbox[^14] | Not stated[^18] |

In the field, the connector overview links to the Microsoft Dynamics 365 article through an authoring preview address rather than a published one[^10].

## Role access matrices

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[^15]. However, this is disputed: the HTTP connector article's prerequisites name 3 roles and its own role table grants access to 6[^16].

## See also

- See also [Webex Contact Center integration connectors](https://warmtransfer.net/knowledge/wxcc-integration-connectors).
- See also [The Microsoft Dynamics 365 and Microsoft Teams connector entries](https://warmtransfer.net/knowledge/wxcc-connector-dynamics-and-teams).
- See also [Which Flow Designer activities can send customer data outside the platform](https://warmtransfer.net/knowledge/wxcc-flow-data-egress).
- See also [The Flow Designer virtual agent activities](https://warmtransfer.net/knowledge/wxcc-virtual-agent-activities).

## Applicability

Applies to: Cisco Webex Contact Center. Sources checked 2026-09-05.

## What remains uncertain

Who may create the 4 connector types that publish no role is not covered by the sources below. Where a connector credential is stored and in what form is not covered by the sources below. Whether a connector secret can be rotated or expires is not covered by the sources below. The Microsoft Dynamics 365 and Microsoft Teams connector articles are not covered by the sources below.

## Sources

[^1]: Cisco states that after a successful connectivity check the system saves the Microsoft Dynamics 365 credentials and displays a confirmation message. Source: [Configure Microsoft Dynamics 365 connector for Webex Contact Center](https://help.webex.com/en-us/article/460fet/Configure-Microsoft-Dynamics-365-connector-for-Webex-Contact-Center), Configure Microsoft Dynamics 365 connector, connectivity check step. Checked 2026-09-05.
[^2]: A Microsoft Dynamics 365 connector record holds a name, a resource domain, a grant type fixed to client credentials with a certificate, a client identifier, a public key certificate, a private key certificate, a token URL and a scope. Source: [Configure Microsoft Dynamics 365 connector for Webex Contact Center](https://help.webex.com/en-us/article/460fet/Configure-Microsoft-Dynamics-365-connector-for-Webex-Contact-Center), Configure Microsoft Dynamics 365 connector, record fields. Checked 2026-09-05.
[^3]: 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.
[^4]: The Microsoft Teams integration is set up through an authorisation and consent flow against Azure and exposes no name, client identifier or secret field in Control Hub. Source: [Integrate Webex Contact Center with Microsoft Teams](https://help.webex.com/en-us/article/n1sztxbb/Integrate-Webex-Contact-Center-with-Microsoft-Teams), Integrate Webex Contact Center with Microsoft Teams, setup procedure. Checked 2026-09-05.
[^5]: The only role the Microsoft Teams integration names is an Azure role, Global Administrator or Privileged Role Administrator, rather than a Control Hub or Webex Contact Center role. Source: [Integrate Webex Contact Center with Microsoft Teams](https://help.webex.com/en-us/article/n1sztxbb/Integrate-Webex-Contact-Center-with-Microsoft-Teams), Integrate Webex Contact Center with Microsoft Teams, prerequisites. Checked 2026-09-05.
[^6]: 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.
[^7]: The custom connector article presents a grant type field under Basic Authentication, having stated a step earlier that grant types exist only for OAuth 2.0 (disputed). 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 steps. Checked 2026-09-05.
[^8]: 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.
[^9]: A custom connector supports Basic Auth, which is the default, or OAuth 2.0 with 3 grant types. 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 Type field. Checked 2026-09-05.
[^10]: 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.
[^11]: 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.
[^12]: 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.
[^13]: Google Contact Center AI credentials are delivered by an email whose subject is CCAI Onboarding Provision Status Update, and the Google project identifier is mapped to Cisco's service account through a hosted form. Source: [Configure Google CCAI connector](https://help.webex.com/en-us/article/9zvadfb/Configure-Google-CCAI-connector), Configure Google CCAI connector, onboarding steps. Checked 2026-09-05.
[^14]: Creating a Webex Contact Center HTTP connector requires ticking a checkbox authorising the connector to read, write, modify and delete data in the Contact Center solution. 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, authorisation step. Checked 2026-09-05.
[^15]: 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.
[^16]: The HTTP connector article's prerequisites name 3 roles and its own role table grants access to 6 (disputed). 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, prerequisites against the role table. Checked 2026-09-05.
[^17]: The HTTP connector article lists UPDATE among the HTTP verbs (field report). 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, scope material. Checked 2026-09-05.
[^18]: Two of the connector articles publish a per-type maximum: 10 custom connectors and 5 Salesforce connectors, with 1 Webex Experience Management connector. Source: [Configure custom connector for Webex Contact Center](https://help.webex.com/en-us/article/n4u702ab/Configure-custom-connector-for-Webex-Contact-Center), Per-type articles, stated maxima. Checked 2026-09-05.
[^19]: A Salesforce connector record holds a name, a client identifier that Salesforce calls a consumer key, an email address, a URL and a private key, and carries no client secret. Source: [Configure Salesforce connector for Webex Contact Center](https://help.webex.com/en-us/article/t2xs2ab/Configure-Salesforce-connector-for-Webex-Contact-Center), Configure Salesforce connector, record fields. Checked 2026-09-05.
[^20]: 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.
[^21]: Of the 5 documented connector types, 2 require the administrator to type no secret at all: Google Contact Center AI, which uses a Google sign-in, and the Webex Contact Center HTTP connector, where the platform mints the identity (inferred). Source: [Create Webex Contact Center HTTP connector](https://help.webex.com/en-us/article/n54f5wd/Create-Webex-Contact-Center-HTTP-connector), Assembled from the 5 per-type articles' record fields. Checked 2026-09-05.
[^22]: A Webex Experience Management connector record holds a name, a description, and the username and API key of a service account. Source: [Configure Webex Experience Management connector for Webex Contact Center](https://help.webex.com/en-us/article/j6ul1k/Configure-Webex-Experience-Management-connector-for-Webex-Contact-Center), Configure Webex Experience Management connector, record fields. Checked 2026-09-05.