Skip to main content

Reconnect Salesforce Service Cloud

Use these steps to reauthorize Assembled's connection to Salesforce Service Cloud. Reconnect each production org and each sandbox separately. You might need to do this after a security incident, when your Salesforce integration user changes, or when syncs fail with an authorization error.

If you're here because of the November 13, 2026 security incident: Reconnect every Salesforce org connected to Assembled, including sandboxes. If you reconnected before November 14 and syncs are failing again, reconnect once more using these steps. 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 Salesforce admin or your dedicated Salesforce integration user, with API access and access to the objects Assembled already syncs. We recommend using a shared integration user rather than a personal account.

Before you start

  • List every Salesforce org connected to Assembled, including sandboxes. You'll reconnect each one separately.
  • Use the same integration user as before, and keep its existing permissions.
  • If you have a custom Salesforce setup, or you use Salesforce Messaging with Assembled, contact Support before you start so we can make sure your settings are kept.

Steps

  1. In Assembled, go to Configure > Third-party integrations and find the Salesforce card. If it still shows Connected, don't select Remove, because that deletes your saved configuration. Instead, contact Support and we'll clear the old connection without deleting your settings. If it shows Not connected, continue.
  2. If Assembled's old authorization still shows as active in Salesforce (for example, under Setup > Connected Apps OAuth Usage), have your Salesforce admin revoke it before you reconnect.
  3. In Configure > Third-party integrations, select Available, then select Connect integration on the Salesforce card. Sign in as your Salesforce admin or integration user and approve access.
  4. Repeat for each sandbox. Sign in with that sandbox's login, not your production login.
  5. Check that each Salesforce card shows Connected and that its sync rows are progressing.

    The Salesforce card on Configure > Third-party integrations with a Connected tag, a Backfill in progress note, the Manage queues, mappings, and exclusions button, and the Instance, Scope, and Authorized rows

How to confirm it's working

  • On each Salesforce card, check for a recent successful sync. The Connected tag on its own doesn't confirm that data is flowing.
  • Compare recent case volume and agent states in Assembled with what you see in Salesforce.
  • 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 cases and most contact objects from Salesforce every 5 minutes, and agent states about every 30 seconds. Sandboxes follow the same schedule. 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 Salesforce history automatically, and the Salesforce card shows Backfill in progress while it runs. If you use Salesforce Messaging or have customized your Salesforce settings in Assembled, contact Support before requesting any extra backfill so we can check your settings first. If you still see gaps from while Salesforce was disconnected, let us know which dates and objects are affected.

Things to watch for

  • Don't select Remove on a connected Salesforce card. It deletes your saved configuration, including Salesforce Messaging settings. Contact Support instead.
  • Reconnect every org. Each production org and sandbox has its own connection, so reconnect each one.
  • Reconnect again if syncs start failing. If syncs fail with errors such as invalid_grant or INVALID_SESSION_ID after you reconnected, reconnect again.
  • Keep the integration user's permissions. Removing access to objects Assembled already syncs will cause those syncs to fail.

For more about how the integration works, see Salesforce Service Cloud integration.

Need help?

If something doesn't look right, contact our Support team and include any error text you see on the Salesforce card. Please don't send passwords or tokens by email or chat.

Still have questions?