Use these steps to replace the Gladly API token that Assembled uses to connect to your Gladly account. You might do this after a security incident, when a Gladly admin leaves, or as part of regular credential rotation.
If you're here because of the November 13, 2026 security incident: Assembled can't revoke Gladly API tokens from our side, so please replace your token using the steps below. Pausing or disabling the integration in Assembled doesn't make the old token stop working. Only deleting it in Gladly 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 Gladly admin who can create and delete API tokens. We recommend using a shared service account rather than a personal one.
Before you start
- Have your Gladly subdomain ready, plus the email address of the Gladly user who will own the new token.
- Note any custom Gladly settings you've set up in Assembled, such as queue rules and agent state mappings. Reconnecting uses what you enter in the connect form, so you'll want to check these afterward.
Steps
- In Gladly, go to Settings > API Tokens and create a new API token for the user Assembled connects with. Don't delete the old token yet.
- In Assembled, go to Configure > Third-party integrations. On the Gladly card, open the menu and choose Disable integration. This removes the old token from Assembled and pauses Gladly syncs. The Gladly data already in Assembled stays where it is.
- Gladly now appears with the integrations you can connect. Select Configure integration, then enter the email of the Gladly user who owns the new token, the new API token, and your Gladly subdomain. If this is a sandbox account, select Sandbox instance. Then select Connect with Gladly.
-
On the reconnected Gladly card, select Connect webhook to turn the contact webhook back on. A new connection starts without it.
- Back in Gladly, delete the old API token. If an old Assembled webhook still appears in Gladly's webhook settings, delete it too.
How to confirm it's working
- On the Gladly card in Configure > Third-party integrations, check for a recent successful sync. The Connected tag on its own doesn't confirm that data is flowing.
- Check that the Contact webhook row no longer shows a Connect webhook button.
- In Gladly, check that the old API token no longer appears in your list of tokens.
When you'll see data
Assembled reads contacts from Gladly every 30 minutes. If you've turned on the contact and agent status webhooks, they send updates as they happen. After you reconnect, allow time for the next scheduled sync. Reports can take a little longer to refresh.
Restoring missed data
Reconnecting normally starts a backfill of your Gladly history automatically. If you've customized Gladly mappings or settings in Assembled, contact Support before requesting any extra backfill so we can check your settings first. If you still see gaps from while Gladly was disconnected, let us know which dates are affected and we'll help.
Things to watch for
- Create the new token first. That way you can reconnect right after you disable the integration, and syncs pause for as short a time as possible.
- Use Disable integration to swap the token. There's no option to edit the token on a connected Gladly card.
- Use the right email. Enter the email of the Gladly user who created the new token.
- Turn your webhooks back on. Select Connect webhook after reconnecting. If you also set up the agent status webhook in Gladly, check that it's still enabled. See Gladly integration for setup steps.
- Delete the old token in Gladly. Disabling or pausing the integration in Assembled doesn't invalidate it.
Need help?
If something doesn't look right, contact our Support team and include any error text you see on the Gladly card. Please don't send API tokens or passwords by email or chat.