After the connector is saved, flows use it through the HTTP Request activity and the credential service keeps the OAuth token valid without flow logic.
Checked 2026-09-30
Flow developers need not be concerned about managing the access token after creating the connector
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- connectors
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Configure custom connector for Webex Contact Center — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · Configure custom connector, closing paragraph
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up the Webex Contact Center connector for ServiceNow: source note wxcc-servicenow-setup-custom-connector-token. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-servicenow-setup-custom-connector-token
BibTeX
@misc{warmtransfer-claim-wxcc-servicenow-setup-custom-connector-token,
title = {Setting up the Webex Contact Center connector for ServiceNow: source note wxcc-servicenow-setup-custom-connector-token},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-servicenow-setup-custom-connector-token},
note = {Source note wxcc-servicenow-setup-custom-connector-token, checked 2026-09-30}
}