Use these steps to replace the Kustomer API key that Assembled uses to connect to your Kustomer account. You might do this after a security incident, when a Kustomer 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 Kustomer API keys from our side, so please replace your key using the steps below. Pausing or disabling the integration in Assembled doesn't make the old key stop working. Only deleting it in Kustomer 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 Kustomer admin who can create and delete API keys. We recommend using a shared service account rather than a personal one.
Before you start
- Check which permissions the new key needs. They're listed on the Kustomer connection form in Assembled and in Kustomer integration. If your AI agents use Kustomer, include the AI and webhook permissions too.
- Note any custom Kustomer settings you've set up in Assembled, such as queue rules and mappings, so you can check them afterward.
Steps
- In Kustomer, have your admin create a new API key with the permissions Assembled needs. Don't delete the old key yet.
- In Assembled, go to Configure > Third-party integrations. On the Kustomer card, open the menu and choose Disable integration.
-
Kustomer now appears with the integrations you can connect. Select Configure integration, enter the new API key, and select Connect with Kustomer. You don't need to choose a region, because Assembled reads it from the key.
-
If your AI agents use Kustomer and the card shows Outbound webhook isn't enabled, select Create webhook, then check that it shows Enabled.
- Back in Kustomer, delete the old API key.
How to confirm it's working
- On the Kustomer card, check for a recent successful sync. The Connected tag on its own doesn't confirm that data is flowing.
- Check that recent conversations and agent states appear in Assembled.
- 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 Kustomer conversations every minute and agent states about every 30 seconds. 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 Kustomer history automatically. While it runs, the card shows Backfill in progress, and when it's done it shows the date it's backfilled until. If you still see gaps from while Kustomer was disconnected, contact Support and let us know which dates are affected.
Things to watch for
- Give the new key every permission listed. Assembled doesn't check permissions when you connect, so a key that's missing one can connect but then fail to sync. Check the sync rows after you reconnect.
- Create the new key first. That way you can reconnect right after you disable the integration, and syncs pause for as short a time as possible.
- Turn your webhook back on. If your AI agents use Kustomer, check that Outbound webhook shows Enabled.
- Delete the old key in Kustomer. 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 Kustomer card. Please don't send API keys or passwords by email or chat.