To replace the OAuth client secret Assembled uses to connect to Genesys Cloud, you create a new one in Genesys Cloud, and our Support team helps you update it in Assembled. How it's updated depends on how your connection was set up, so please contact Support before you change anything.
If you're here because of the November 13, 2026 security incident: Assembled can't revoke Genesys Cloud credentials from our side, so please replace yours using these steps. Pausing or disconnecting the integration in Assembled doesn't stop the old OAuth client secret from working. Only retiring it in Genesys Cloud does. For more about the incident, see November 13, 2026 security incident.
Who does this
- An Assembled admin, or someone with a role that can configure third-party integrations.
- A Genesys Cloud admin who manages the OAuth client Assembled uses.
Before you start
- Contact Support and tell us which Genesys Cloud accounts you use with Assembled, including any test or sandbox accounts. Don't send credentials by email or chat.
- Find the OAuth client in Genesys Cloud that Assembled uses, along with its client ID and your base URL.
Steps
- Contact Support. We'll confirm which OAuth client secret Assembled uses for your account and how to update it.
- In Genesys Cloud, have your admin create a new client secret for that OAuth client, or create a new OAuth client with the same permissions.
- Support will send you a secure link to provide the client ID, the new client secret, and your base URL, and we'll update the connection for you. Never send the secret by email. Don't remove the integration or set it up again from scratch, because that can delete your saved settings.
- Once the new OAuth client secret is working, have your Genesys Cloud admin retire the old client secret, or disable the old OAuth client if you created a new one.
-
Check the Genesys card in Configure > Third-party integrations for new agent state and ticket syncs.
How to confirm it's working
- On the Genesys card, check for recent successful syncs. The Connected tag on its own doesn't confirm that data is flowing.
- Compare recent calls and agent states in Assembled with what you see in Genesys Cloud.
- If a sync row is red, hover over it to see the error, and send that error text to Support.
When you'll see data
Assembled syncs Genesys Cloud conversations and agent states about every 30 seconds. After the connection is updated, allow time for the next scheduled sync. Reports can take a little longer to refresh.
Restoring missed data
Updating the connection normally starts a backfill of your Genesys Cloud history automatically, and the card shows Backfill in progress while it runs. If you still see gaps from while the connection wasn't working, contact Support with the dates affected.
Things to watch for
- Contact Support first. We'll confirm the right way to update your connection before you change anything.
- Don't remove the integration. Removing it or setting it up again from scratch can delete your saved settings.
- Retire the old OAuth client secret in Genesys Cloud. Disconnecting or pausing the integration in Assembled doesn't stop it from working.
- Keep the same access. Give the new OAuth client secret the same permissions as the old one, or syncs can fail.
- Never email the secret. Use the secure link Support sends you.
For more about how the integration works, see Genesys Cloud integration.
Need help?
If something doesn't look right, contact our Support team and include any error text you see. Please don't send API keys, tokens, or secrets by email or chat.