What each Webex Contact Center connector type stores

Verified 2026-09-05 · 22 claims · sources tier 2 · 2 disputed

Also known as Billable Project Name, Resource Domain URL, Webex Contact Center credential service.

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.

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.
• See also The Microsoft Dynamics 365 and Microsoft Teams connector entries.
• See also Which Flow Designer activities can send customer data outside the platform.
• See also The Flow Designer virtual agent activities.

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.

What remains uncertain

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

WarmTransfer. (2026, September 5). What each Webex Contact Center connector type stores. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-connector-types

@misc{warmtransfer-wxcc-connector-types,
  title  = {What each Webex Contact Center connector type stores},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-connector-types},
  note   = {Verified 2026-09-05}
}