topic Re: Custom CRM Connector development using Cisco WebEx Contact Center in Webex for Developers

Custom CRM Connector development using Cisco WebEx Contact Center API

pravin1 — Tue, 14 Mar 2023 14:39:44 GMT

Hi Team,

We have developed custom CRM connector for Cisco Finesse UCCX and UCCE using Finesse rest API's which send call data when call arrives to CRM to screen popup. Similarly we want to develop custom connect for WebEx Cloud contact center. Please let me know which API's we need to use. Are there any sample code available to refer. Also is there Sandbox lab available for development and testing purpose.

Regards,

Pravin

Re: Custom CRM Connector development using Cisco WebEx Contact Center

bill.king1 — Wed, 15 Mar 2023 20:31:11 GMT

Hi, the last note I saw said it is still coming, see this link.
https://community.cisco.com/t5/contact-center/request-for-webex-contact-center-sandbox/td-p/4740662

Re: Custom CRM Connector development using Cisco WebEx Contact Center

Arunabh Bhattacharjee — Wed, 05 Apr 2023 00:01:17 GMT

Hello @pravin1 ,

To develop CRM connectors you can use 2 approaches:

1. iFrame the Desktop and build a headless widget using the desktop JS SDK.

https://developer.webex-cx.com/documentation/guides/desktop

2. build your own app (front end) and leverage the Agent Desktop REST APIs and Websocket connection

https://developer.webex-cx.com/documentation/agents

https://developer.webex-cx.com/documentation/tasks

https://developer.webex-cx.com/documentation/guides/contact-control-apis

There are several samples to get started with JS SDK Widgets in the API samples repo, and the Desktop REST API sample as well

https://github.com/CiscoDevNet/webex-contact-center-api-samples

These are free 101 samples aimed at getting you started and help you extend or reuse.

Thanks & Regards,

Arunabh.

Re: Custom CRM Connector development using Cisco WebEx Contact Center

Schreuder Software — Wed, 22 Nov 2023 00:52:16 GMT

Hey Arunabh,

Is there anything on the roadmap for allowing partners to develop custom Flow Elements? We'd like to do make several REST requests in the same HTTP Request element to simplify the Flows for our customers. This would be similar to Cisco Voice Portal's support for custom Java Elements.

Thanks!

Re: Custom CRM Connector development using Cisco WebEx Contact Center

Arunabh Bhattacharjee — Mon, 27 Nov 2023 02:55:45 GMT

Hi Schreuder,

Thanks for the details, Could you please unicast message me 1:1 with the sample list of http calls, or exact orchestration of those calls, so that we can better confirm availability.

Reason being, the subflow feature is coming soon, and the “custom compute node” for flow is on our immediate roadmap. Hence confirming those details will better help understand which solution might be viable in the short term once subflows is released.

If none of those upcoming will serve the same purpose then we can add it to the backlog.

Thanks and Regards,
Arunabh

Re: Custom CRM Connector development using Cisco WebEx Contact Center

david.macias — Mon, 27 Nov 2023 20:55:27 GMT

@Arunabh Bhattacharjee Great to hear that custom nodes will be supported soon, can you share any details around them and rough ETA?

david

Re: Custom CRM Connector development using Cisco WebEx Contact Center

Arunabh Bhattacharjee — Mon, 27 Nov 2023 21:03:50 GMT

David at this time we can only provide calendar year guidance, it is on the roadmap for CY2024.
We will publish the roadmap as a part of our assets on SalesConnect and will likely flesh out more realistic dates as we approach the delivery timeline.

Thanks & Regards,
Arunabh.

Re: Custom CRM Connector development using Cisco WebEx Contact Center

david.macias — Mon, 27 Nov 2023 21:07:26 GMT

You tease! I figured as such. Can you share any details around the functionality that this will provide?

david

Re: Custom CRM Connector development using Cisco WebEx Contact Center

Amr7 — Wed, 05 Feb 2025 11:31:59 GMT

Hi Arunabh,
How can I iframe the Webex URL? It returns this error:
Refused to frame 'https://desktop.wxcc-eu1.cisco.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'