Cisco first-party Webex Contact Center repositories
Verified 2026-10-14 · 59 sources · tier 2–3
Also known as wxcc-github-samples.
On 2026-10-14, a search of the CiscoDevNet organization for webex-contact-center returned 6 repositories, and a search of the WebexSamples organization for contact-center returned 4 repositories 19 56. The GitHub organisations WebexSamples and webex are not domain-verified on GitHub, unlike CiscoDevNet and cisco, so first-party status for repositories under them rests on stated identity rather than platform verification 2.
Repository inventory
The CiscoDevNet search returned these repositories: widget-starter, provider-sample-code, dbconnector, crm-integrations, ai-sample-code and apps 19.
The WebexSamples search returned these repositories: webex-contact-center-api-samples, webex-contact-center-flows, webex-ai-cookbook and webex-contact-center-agent-desktop-api-sample 56.
The developer documentation also points to webex/dataSourceSchemas, which describes itself as a read-only repository where only Webex internal teams can publish schema definitions 17 26.
Flow templates: webex-contact-center-flows
The WebexSamples webex-contact-center-flows repository describes itself as the official repository for sample Webex Contact Center flow templates that are usable in Flow Designer 3 36. It was last pushed on 19 August 2026 3.
The repository contains these top-level template folders: 29 35 38 31
- AI agent folders: ai-agent-autonomous, ai-agent-scripted-track-package and ai_agent_scripted_doctors_appointment 29.
- Outbound folders: outbound-ivr-campaign, outbound-predictive-progressive and outbound-preview 35.
- Subflow folders: subflow-callback, subflow-error, subflow-http, subflow-queue-treatment and subflow-register-scheduled_callback 38.
- HTTP data dip folders for Microsoft Dynamics, Salesforce, ServiceNow and Zendesk 31.
The contribution guidance expects each template folder to contain a template JSON file, a template-body-filled.json file and a README 39. Direct pushes to the main branch are not allowed, and contributors work from a fork or a branch 33. The README says templates are submitted through a Flow Team member for production and cross-data-centre deployment 32. The README also states that the repository assumes template creators have fully tested their templates and that it posts the assets as is 30.
The Flow Designer help article lists flow templates including Hello World, Simple inbound call to queue, Menu auto attendant, Last agent routing and 3 AI Agent templates 42. It also lists subflow templates for collecting callback information, error handling, HTTP data dip, queue treatment and scheduled callback 44. We infer that the in-product Flow Designer templates are probably published from webex-contact-center-flows, because the help article's template names match the repository folders and the README describes promotion to production by the Flow Team 43.
API samples: webex-contact-center-api-samples
WebexSamples/webex-contact-center-api-samples describes itself as the official code samples and snippets repository for the Webex Contact Center APIs 11. It has top-level folders for reporting, call recording, callbacks, token management, widgets and AI agent fulfilment flows, among others 8. To get started, you create an App Integration on the Webex Developer Portal to get an OAuth2 client ID and client secret 10. The README presents the samples as demos for learning and says production solutions should take a security-first approach to architecture and design 12.
AI, BYoVA and media forking
CiscoDevNet/webex-contact-center-ai-sample-code has 2 top-level folders: provider-api and serving-api 6. The provider-api folder holds only a notice that the dialog-connector-simulator code moved to media-service-api in CiscoDevNet/webex-contact-center-provider-sample-code 5. The repository README sends readers to a separate Media Service API sample code repository for virtual agent, media forking and real-time transcript references 4.
CCAI Serving API sample
The CCAI Serving API sample runs against a gRPC server, and clients connect with a gRPC client or from a browser using grpc-web 54. The README gives the gRPC endpoint pattern serving-api-streaming.wxcc-{data-center}.cisco.com:443, with us1 as the example data centre 53. It requires an access token from the organization's machine account with the scopes cjp-ccai:read and cjp:organization in the Authorization header 55.
Provider sample code
CiscoDevNet/webex-contact-center-provider-sample-code holds reference implementations and integration guides for the Media Service APIs that Webex Contact Center exposes to providers, partners and customers 52. It lists 4 prerequisites: a Webex Contact Center tenant, an authorized Webex Service App, a registered data source and a Control Hub flow 51. The code requires runtime JWS/JWT validation of inbound calls and supports mTLS as an extra transport-layer check 48. The README specifies 8 kHz or 16 kHz mono audio in Linear16 or G.711 mu-law, and media forking also supports A-law 45.
The repository covers Bring Your Own Virtual Agent over 2 transports: gRPC bidirectional streaming with Protobuf, and WebSocket with JSON text frames 46. The developer portal's Bring Your Own Virtual Agent page links to this repository as the sample code and the Dialog Connector Simulator reference 14. The BYoVA over gRPC documentation says the CiscoDevNet sample repository provides Java and Python reference implementations 15. The developer documentation states that the Java and Python BYoVA reference connectors listen on port 8086 by default 18. Cisco's BYoVA documentation states that the sample connector only demonstrates the protocol, and that the partner remains responsible for hosting, scaling, securing and supporting the production service 16.
Real-time media forking in the provider sample code supports only gRPC bidirectional streaming, with Webex Contact Center as the gRPC client and the partner service implementing the ConversationAudio server 47. The Python media forking folder is only a scaffold, with implementation in progress and no runtime code, and the Java Spring Boot simulator is the runnable media forking sample 40. The media forking README says to register the data source with the media forking schema UUID, not the BYoVA schema UUID 41.
Data source schemas
The BYoVA developer documentation points developers to the Voice Virtual Agent protobuf definitions in the webex/dataSourceSchemas repository 17. webex/dataSourceSchemas holds Bring Your Own Data Source schemas for 2 use cases: Voice Virtual Agent (BYoVA) and Media Forking 27.
Desktop widgets, data connectors and CRM layouts
CiscoDevNet/webex-contact-center-widget-starter provides Agent and Supervisor Desktop widget starters for React, Angular and a pure Web Component approach built on Lit Element 59. Its README tells developers to install the @wxcc-desktop/sdk package with npm or yarn and import Desktop from it 58. According to the widget starter README, third-party custom widgets loaded from an untrusted absolute script URL are wrapped in a sandboxed iframe in Desktop 57.
CiscoDevNet/webex-contact-center-dbconnector lets Webex Contact Center Flow Designer reach SQL data sources 24. Release v2.1.1, dated 2026-03-03, added SQL and LDAP endpoint support across the admin, test and deploy workflows 25.
The webex-contact-center-crm-integrations README describes its contents as legacy Version 1 desktop layouts and companion assets for Webex Contact Center CRM integrations 21.
Documentation-only, dormant and archived repositories
WebexSamples/webex-ai-cookbook is a documentation-first sample repository for Webex AI agents and Webex Contact Center flow patterns, with no setup or run instructions in its README 20. CiscoDevNet/webex-contact-center-apps was last updated on 2022-12-20, has 6 commits, and has a README with only a title 13. The WebexSamples repository named ucmtowxc-migrationapi, whose name signals a Unified CM to Webex Calling migration API, is archived with a last push of 3 July 2023 and carries no description or licence 1.
Licensing and support
The repositories do not share one licence or one support path: 22 24 23 9
- webex-contact-center-flows is licensed under the Cisco Sample Code License Version 1.1, and under that licence its sample code is not supported by Cisco TAC and is not tested for quality or performance 37 34.
- webex-contact-center-api-samples is licensed under the Cisco Sample Code License Version 1.1, which states that the code is not supported by Cisco TAC 9. Its README sends dedicated developer support to a ticket on developer.webex.com and discussion to the Webex Contact Center APIs developer community 7.
- webex-contact-center-provider-sample-code is licensed under the Cisco Sample Code License v1.1 49. Its README says the code is for reference and learning, is not meant for production use as is, and is not covered by any Cisco support contract 50.
- webex-contact-center-dbconnector is MIT-licensed 24.
- webex-contact-center-crm-integrations is licensed under the Mozilla Public License 2.0, not the Cisco Sample Code License used by the WebexSamples flow and API sample repositories 22. Its README sends support cases to Cisco TAC and implementation questions to the Cisco Developer Community 23.
See also
- Webex Contact Center Flow Designer architecture
- Webex Contact Center APIs and webhooks
- Webex Contact Center AI agent assist and virtual agents
- Webex Contact Center Agent Desktop and widgets
- Webex Contact Center preview and progressive outbound campaigns
Applicability
Applies to: Cisco Webex Contact Center, Cisco Webex Calling, and Cisco Webex. Deployments: cloud and multi-tenant. Sources checked 2026-10-14. The repository inventory reflects searches run on 2026-10-14 19 56. The dbconnector LDAP endpoint support applies from release v2.1.1, dated 2026-03-03 25. The crm-integrations repository covers legacy Version 1 desktop layouts 21.
What remains uncertain
The contents, licence and support terms of webex-contact-center-agent-desktop-api-sample are not covered by the sources below. The licence and support terms of webex-contact-center-widget-starter, webex-contact-center-ai-sample-code, webex-ai-cookbook and webex/dataSourceSchemas are not covered by the sources below. Whether the in-product Flow Designer templates are actually published from webex-contact-center-flows is not confirmed by any source, and we infer it only from matching names and the README's description of Flow Team promotion 43. Whether the provider-sample-code reference connectors have been tested for production load is not covered by the sources below.
See also
Sampled by
- Webex Contact Center Flow Designer architecture — Inbound relationship. Cisco publishes sample flow templates in WebexSamples/webex-contact-center-flows and the folder names match the template list in the Flow Designer help article.
Supports
- Webex Contact Center AI agent assist and virtual agents — The CCAI provider and serving API samples live in a CiscoDevNet repository
- Webex Contact Center APIs and webhooks — WebexSamples/webex-contact-center-api-samples is the official samples repository for the Webex Contact Center APIs.
- Webex Contact Center Agent Desktop and widgets — CiscoDevNet/webex-contact-center-widget-starter is the starter kit for Agent Desktop and Supervisor Desktop widgets.
Referenced by
- Webex Contact Center Flow Designer architecture — Cisco publishes sample flow templates
Sources
- 1The WebexSamples repository named ucmtowxc-migrationapi, whose name signals a Unified CM to Webex Calling migration API, is archived with a last push of 3 July 2023 and carries no description or licence.WebexSamples/ucmtowxc-migrationapi · GitHub API archived, pushed_at, description and license fields · Checked 2026-09-04
- 2The GitHub organisations WebexSamples and webex are not domain-verified on GitHub, unlike CiscoDevNet and cisco, so first-party status for repositories under them rests on stated identity rather than platform verification.WebexSamples/webex-contact-center-flows · GitHub API organization is_verified field for each org · Checked 2026-09-04
- 3The WebexSamples webex-contact-center-flows repository self-describes as the official repository of sample Webex Contact Center flow templates usable in Flow Designer, and was last pushed on 19 August 2026.WebexSamples/webex-contact-center-flows · GitHub API repository description and pushed_at fields · Checked 2026-09-04
- 4The webex-contact-center-ai-sample-code README sends readers to a separate Media Service API sample code repository for virtual agent, media forking and real-time transcript references.CiscoDevNet/webex-contact-center-ai-sample-code · README, pointer to Media Service API Sample Code · Checked 2026-10-14
- 5The provider-api folder in webex-contact-center-ai-sample-code holds only a notice that the dialog-connector-simulator code moved to media-service-api in CiscoDevNet/webex-contact-center-provider-sample-code.webex-contact-center-ai-sample-code provider-api folder · provider-api/README.md · Checked 2026-10-14
- 6CiscoDevNet/webex-contact-center-ai-sample-code has two top-level folders: provider-api and serving-api.CiscoDevNet/webex-contact-center-ai-sample-code · Top-level folder listing · Checked 2026-10-14
- 7The webex-contact-center-api-samples README sends dedicated developer support to a ticket on developer.webex.com and discussion to the Webex Contact Center APIs developer community.WebexSamples/webex-contact-center-api-samples · README support section · Checked 2026-10-14
- 8webex-contact-center-api-samples has top-level folders for reporting, call recording, callbacks, token management, widgets and AI agent fulfilment flows, among others.WebexSamples/webex-contact-center-api-samples · Top-level folder listing · Checked 2026-10-14
- 9webex-contact-center-api-samples is licensed under the Cisco Sample Code License Version 1.1, which states that the code is not supported by Cisco TAC.webex-contact-center-api-samples LICENSE · LICENSE file title and support clause · Checked 2026-10-14
- 10To get started with webex-contact-center-api-samples, you create an App Integration on the Webex Developer Portal to get an OAuth2 client ID and client secret.WebexSamples/webex-contact-center-api-samples · README getting started section · Checked 2026-10-14
- 11WebexSamples/webex-contact-center-api-samples describes itself as the official code samples and snippets repository for the Webex Contact Center APIs.WebexSamples/webex-contact-center-api-samples · Repository About description · Checked 2026-10-14
- 12The webex-contact-center-api-samples README presents the samples as demos for learning and says production solutions should take a security-first approach to architecture and design.WebexSamples/webex-contact-center-api-samples · README disclaimer · Checked 2026-10-14
- 13CiscoDevNet/webex-contact-center-apps was last updated on 2022-12-20, has 6 commits, and has a README with only a title.CiscoDevNet/webex-contact-center-apps · Repository page commit count and README; CiscoDevNet listing updated date · Checked 2026-10-14
- 14The developer portal's Bring Your Own Virtual Agent page links to CiscoDevNet/webex-contact-center-provider-sample-code as the sample code and the Dialog Connector Simulator reference.Bring Your Own Virtual Agent · Phase 1 - Development, steps 4 and the Dialog Connector Simulator reference · Checked 2026-10-14
- 15The BYoVA over gRPC documentation says the CiscoDevNet sample repository provides Java and Python reference implementations.Bring Your Own Virtual Agent over gRPC · Overview · Checked 2026-10-14
- 16Cisco's BYoVA documentation states that the sample connector only demonstrates the protocol. The partner remains responsible for hosting, scaling, securing and supporting the production service.Bring Your Own Virtual Agent over gRPC · Adapt and verify the connector · Checked 2026-10-14
- 17The Bring Your Own Virtual Agent developer documentation points developers to the Voice Virtual Agent protobuf definitions in the webex/dataSourceSchemas repository.Bring Your Own Virtual Agent over gRPC · Overview · Checked 2026-10-14
- 18The developer documentation states that the Java and Python BYoVA reference connectors listen on port 8086 by default.Bring Your Own Virtual Agent over gRPC · Run a reference connector · Checked 2026-10-14
- 19On 2026-10-14, a search of the CiscoDevNet organization for webex-contact-center returned six repositories: widget-starter, provider-sample-code, dbconnector, crm-integrations, ai-sample-code and apps.CiscoDevNet repositories matching webex-contact-center · Repository rows in listing · Checked 2026-10-14
- 20WebexSamples/webex-ai-cookbook is a documentation-first sample repository for Webex AI agents and Webex Contact Center flow patterns, with no setup or run instructions in its README.WebexSamples/webex-ai-cookbook · Repository About description; README · Checked 2026-10-14
- 21The webex-contact-center-crm-integrations README describes its contents as legacy Version 1 desktop layouts and companion assets for Webex Contact Center CRM integrations.CiscoDevNet/webex-contact-center-crm-integrations · README introduction · Checked 2026-10-14
- 22webex-contact-center-crm-integrations is licensed under the Mozilla Public License 2.0, not the Cisco Sample Code License used by the WebexSamples flow and API sample repositories.CiscoDevNet/webex-contact-center-crm-integrations · Repository license · Checked 2026-10-14
- 23The webex-contact-center-crm-integrations README sends support cases to Cisco TAC and implementation questions to the Cisco Developer Community.CiscoDevNet/webex-contact-center-crm-integrations · README support section · Checked 2026-10-14
- 24CiscoDevNet/webex-contact-center-dbconnector lets Webex Contact Center Flow Designer reach SQL data sources and is MIT-licensed.CiscoDevNet/webex-contact-center-dbconnector · Repository About description and license · Checked 2026-10-14
- 25dbconnector release v2.1.1, dated 2026-03-03, added SQL and LDAP endpoint support across the admin, test and deploy workflows.CiscoDevNet/webex-contact-center-dbconnector · README recent update v2.1.1 · Checked 2026-10-14
- 26webex/dataSourceSchemas describes itself as a read-only repository where only Webex internal teams can publish schema definitions.webex/dataSourceSchemas · README · Checked 2026-10-14
- 27webex/dataSourceSchemas holds Bring Your Own Data Source schemas for two use cases: Voice Virtual Agent (BYoVA) and Media Forking.webex/dataSourceSchemas · README supported use cases · Checked 2026-10-14
- 28The developer portal's BYoVA proto link, a v1.2 path, may not point at the newest schema release, because the dataSourceSchemas README example URIs reference tag v1.8.inferredwebex/dataSourceSchemas · README example URIs compared with webex-dev-byova Phase 1 step 3 link · Checked 2026-10-14
- 29webex-contact-center-flows contains AI agent template folders named ai-agent-autonomous, ai-agent-scripted-track-package and ai_agent_scripted_doctors_appointment.WebexSamples/webex-contact-center-flows · Top-level folder listing · Checked 2026-10-14
- 30The webex-contact-center-flows README states that the repository assumes template creators have fully tested their templates and that it posts the assets as is.WebexSamples/webex-contact-center-flows · README disclaimer · Checked 2026-10-14
- 31webex-contact-center-flows contains HTTP data dip template folders for Microsoft Dynamics, Salesforce, ServiceNow and Zendesk.WebexSamples/webex-contact-center-flows · Top-level folder listing · Checked 2026-10-14
- 32The webex-contact-center-flows README says templates are submitted through a Flow Team member for production and cross-data-centre deployment.WebexSamples/webex-contact-center-flows · README contribution section · Checked 2026-10-14
- 33Direct pushes to the main branch of webex-contact-center-flows are not allowed. Contributors work from a fork or a branch.WebexSamples/webex-contact-center-flows · README contribution section · Checked 2026-10-14
- 34Under its license, the sample code in webex-contact-center-flows is not supported by Cisco TAC and is not tested for quality or performance.webex-contact-center-flows LICENSE · LICENSE support and warranty clause · Checked 2026-10-14
- 35webex-contact-center-flows contains outbound template folders named outbound-ivr-campaign, outbound-predictive-progressive and outbound-preview.WebexSamples/webex-contact-center-flows · Top-level folder listing · Checked 2026-10-14
- 36The WebexSamples/webex-contact-center-flows repository describes itself as the official repository for sample Webex Contact Center flow templates that are usable on Flow Designer.WebexSamples/webex-contact-center-flows · Repository About description · Checked 2026-10-14
- 37webex-contact-center-flows is licensed under the Cisco Sample Code License Version 1.1.webex-contact-center-flows LICENSE · LICENSE file title · Checked 2026-10-14
- 38webex-contact-center-flows contains subflow template folders named subflow-callback, subflow-error, subflow-http, subflow-queue-treatment and subflow-register-scheduled_callback.WebexSamples/webex-contact-center-flows · Top-level folder listing · Checked 2026-10-14
- 39The webex-contact-center-flows contribution guidance expects each template folder to contain a template JSON file, a template-body-filled.json file and a README.WebexSamples/webex-contact-center-flows · README contribution section · Checked 2026-10-14
- 40The Python media forking folder in the provider sample code is only a scaffold, with implementation in progress and no runtime code. The Java Spring Boot simulator is the runnable media forking sample.webex-contact-center-provider-sample-code media-forking README · media-forking/README.md reference implementations section · Checked 2026-10-14
- 41The media forking README says to register the data source with the media forking schema UUID, not the BYoVA schema UUID.webex-contact-center-provider-sample-code media-forking README · media-forking/README.md onboarding section · Checked 2026-10-14
- 42The Flow Designer help article lists flow templates including Hello World, Simple inbound call to queue, Menu auto attendant, Last agent routing and three AI Agent templates.Build and manage flows with Flow Designer · Section 'Use flow templates' · Checked 2026-10-14
- 43The in-product Flow Designer templates are probably published from the webex-contact-center-flows repository, because the help article's template names match the repository folders and the README describes promotion to production by the Flow Team.inferredWebexSamples/webex-contact-center-flows · README contribution section compared with the help article section 'Use flow templates' · Checked 2026-10-14
- 44The Flow Designer help article lists subflow templates for collecting callback information, error handling, HTTP data dip, queue treatment and scheduled callback.Build and manage flows with Flow Designer · Section 'Use subflow templates' · Checked 2026-10-14
- 45The provider sample code README specifies 8 kHz or 16 kHz mono audio in Linear16 or G.711 mu-law, and media forking also supports A-law.CiscoDevNet/webex-contact-center-provider-sample-code · README audio constraints section · Checked 2026-10-14
- 46The provider sample code repository covers Bring Your Own Virtual Agent over two transports: gRPC bidirectional streaming with Protobuf, and WebSocket with JSON text frames.CiscoDevNet/webex-contact-center-provider-sample-code · README features section · Checked 2026-10-14
- 47Real-time media forking in the provider sample code supports only gRPC bidirectional streaming. Webex Contact Center is the gRPC client and the partner service implements the ConversationAudio server.webex-contact-center-provider-sample-code media-forking README · media-forking/README.md transport section · Checked 2026-10-14
- 48The provider sample code requires runtime JWS/JWT validation of inbound calls, and supports mTLS as an extra transport-layer check.CiscoDevNet/webex-contact-center-provider-sample-code · README authentication section; mtls-authentication.md · Checked 2026-10-14
- 49webex-contact-center-provider-sample-code is licensed under the Cisco Sample Code License v1.1.CiscoDevNet/webex-contact-center-provider-sample-code · License file named on repository page · Checked 2026-10-14
- 50The provider sample code README says the code is for reference and learning, is not meant for production use as is, and is not covered by any Cisco support contract.CiscoDevNet/webex-contact-center-provider-sample-code · README disclaimer · Checked 2026-10-14
- 51The provider sample code lists four prerequisites: a Webex Contact Center tenant, an authorized Webex Service App, a registered data source and a Control Hub flow.CiscoDevNet/webex-contact-center-provider-sample-code · README prerequisites section · Checked 2026-10-14
- 52CiscoDevNet/webex-contact-center-provider-sample-code holds reference implementations and integration guides for the Media Service APIs that Webex Contact Center exposes to providers, partners and customers.CiscoDevNet/webex-contact-center-provider-sample-code · README introduction · Checked 2026-10-14
- 53The Serving API README gives the gRPC endpoint pattern serving-api-streaming.wxcc-{data-center}.cisco.com:443, with us1 as the example data centre.webex-contact-center-ai-sample-code serving-api folder · serving-api/README.md endpoint section · Checked 2026-10-14
- 54The CCAI Serving API sample runs against a gRPC server, and clients connect with a gRPC client or from a browser using grpc-web.webex-contact-center-ai-sample-code serving-api folder · serving-api/README.md · Checked 2026-10-14
- 55The Serving API README requires an access token from the organization's machine account with the scopes cjp-ccai:read and cjp:organization in the Authorization header.webex-contact-center-ai-sample-code serving-api folder · serving-api/README.md authentication section · Checked 2026-10-14
- 56On 2026-10-14, a search of the WebexSamples organization for contact-center returned four repositories: webex-contact-center-api-samples, webex-contact-center-flows, webex-ai-cookbook and webex-contact-center-agent-desktop-api-sample.WebexSamples repositories matching contact-center · Repository rows in listing · Checked 2026-10-14
- 57According to the widget starter README, third-party custom widgets loaded from an untrusted absolute script URL are wrapped in a sandboxed iframe in Desktop.CiscoDevNet/webex-contact-center-widget-starter · README iframe shell section; Examples/Layouts/Iframe_Shell_Partner_Fixes.json · Checked 2026-10-14
- 58The widget starter README tells developers to install the @wxcc-desktop/sdk package with npm or yarn and import Desktop from it.CiscoDevNet/webex-contact-center-widget-starter · README Desktop JS SDK section · Checked 2026-10-14
- 59CiscoDevNet/webex-contact-center-widget-starter provides Agent and Supervisor Desktop widget starters for React, Angular and a pure Web Component approach built on Lit Element.CiscoDevNet/webex-contact-center-widget-starter · README introduction; top-level folders react, angular and lit-element · Checked 2026-10-14
Documents
Bring Your Own Virtual Agent
Bring Your Own Virtual Agent over gRPC
Build and manage flows with Flow Designer
CiscoDevNet repositories matching webex-contact-center
CiscoDevNet/webex-contact-center-ai-sample-code
CiscoDevNet/webex-contact-center-apps
CiscoDevNet/webex-contact-center-crm-integrations
CiscoDevNet/webex-contact-center-dbconnector
CiscoDevNet/webex-contact-center-provider-sample-code
CiscoDevNet/webex-contact-center-widget-starter
webex-contact-center-ai-sample-code provider-api folder
webex-contact-center-ai-sample-code serving-api folder
webex-contact-center-api-samples LICENSE
webex-contact-center-flows LICENSE
webex-contact-center-provider-sample-code media-forking README
webex/dataSourceSchemas
WebexSamples repositories matching contact-center
WebexSamples/ucmtowxc-migrationapi
WebexSamples/webex-ai-cookbook
WebexSamples/webex-contact-center-api-samples
WebexSamples/webex-contact-center-flows
Cite this page
APA
WarmTransfer. (2026, October 14). Cisco first-party Webex Contact Center repositories. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-github-registry
BibTeX
@misc{warmtransfer-webex-cc-github-registry,
title = {Cisco first-party Webex Contact Center repositories},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-cc-github-registry},
note = {Verified 2026-10-14}
}