If your contact center already runs on Genesys Cloud or NICE CXone, you can put a Convoship assistant in front of those conversations without building a custom bridge. Both connectors are first-class channels: you fill in a short form, paste one webhook URL and signing secret into the provider, and inbound messages flow into the same published runtime that powers every other channel.
Same runtime, native transport
A contact-center connector runs the exact published flow you already test in the simulator. Only the transport differs — so behavior on Genesys or NICE matches your web widget and messaging channels.
Where to set this up
Open your assistant and go to Channels (Operate → Channels). Genesys Cloud and NICE CXone appear as cards alongside web, messaging, and voice. Pick a card to open a short setup wizard; when you finish, Convoship shows the inbound webhook URL and signing secret to paste into the provider, plus a Send test message button.
Genesys Cloud
The Genesys connector uses Open Messaging — Genesys's framework for custom messaging integrations. Inbound consumer messages are delivered to Convoship and signed so we can verify they genuinely came from Genesys; bot replies are sent back to the originating conversation.
- In Convoship, choose Genesys Cloud on the Channels page and pick your region (for example mypurecloud.com).
- In Genesys Cloud, create an OAuth client using the Client Credentials grant, then paste its client ID and secret into Convoship.
- In Genesys Cloud, create an Open Messaging integration and copy its integration ID into Convoship.
- Copy the inbound webhook URL and signing secret Convoship shows you into the Open Messaging integration's inbound settings.
- Click Send test message to confirm a reply is delivered, then route a queue or message flow to the integration.
Convoship is also published as a Genesys AppFoundry listing, so Genesys customers can discover and request the integration directly from the AppFoundry marketplace. The in-product setup above is identical whether you start from AppFoundry or from Convoship.
NICE CXone
The NICE CXone connector uses Digital Engagement (Digital First Omnichannel) custom messaging. Inbound consumer messages on the custom channel are delivered to Convoship and HMAC-signed; bot replies are posted back to the originating thread.
- In Convoship, choose NICE CXone on the Channels page and pick your data-center region (for example na1, eu1, or au1).
- In CXone, create an access key and paste its client ID and secret into Convoship.
- In CXone Digital Engagement, create a custom messaging channel and copy its brand ID and channel ID into Convoship.
- Set the channel's inbound webhook to the URL Convoship shows you, and set its signing secret to the value shown.
- Click Send test message to confirm delivery, then point the channel's routing at the assistant.
What each connector asks for
| Connector | Settings | Credentials |
|---|---|---|
| Genesys Cloud | Region, integration ID | OAuth client ID + secret |
| NICE CXone | Region, brand ID, channel ID | Access-key client ID + secret |
Security and handoff
- Every inbound request is signature-verified against the connection's signing secret; unsigned or mismatched requests are rejected.
- Credentials are stored encrypted and are never shown again after setup — only the field names are visible.
- The signing secret is shown once on creation; a workspace admin can reveal it later to reconfigure the provider, and each reveal is audit-logged.
- When a conversation needs a person, your normal handoff path applies — the assistant can hand off to a live agent or queue in the same contact center.
Publish your assistant before going live. Connectors run the published version, so changes you make in the builder reach Genesys or NICE only after you publish.