Skip to content

Re-authorize your Salesforce account

When to use this guide: Use this guide when expected sync behavior is missing, delayed, or incorrect — especially after disconnecting Salesforce and trying to reconnect.

If you disconnected Salesforce and need to reconnect, or sync is failing with a token error, delete the existing connection in OutboundSync and set it up again with your Connected App credentials.

Common errors this fixes

Section titled “Common errors this fixes”

You may need to reconnect if OutboundSync reports:

Is not valid user tokens.

This error means the Salesforce connection no longer has valid tokens — often after a disconnect or an incomplete reconnect.

For BAD_REFRESH_TOKEN errors, see Getting a Bad Refresh Token error.

Reconnect your Salesforce account

Section titled “Reconnect your Salesforce account”
  1. Log in to OutboundSync.
  2. Go to Connected Accounts → Salesforce.
  3. Delete the existing Salesforce connection. If you already tried reconnecting and are stuck in a loop, fully delete the connection before trying again.
  4. Re-enter your Connected App Consumer Key, Consumer Secret, and Salesforce domain (for example, https://yourcompany.my.salesforce.com).
  5. Click Create, then click Connect and complete the Salesforce sign-in flow. Select Allow on the permissions screen.
Create Salesforce connection in OutboundSync Click Connect on the Salesforce account in OutboundSync

For where to find your Consumer Key, Consumer Secret, and domain — and screenshots of each step — see Connect app in OutboundSync in the Salesforce setup guide.

SSO and integration users

Section titled “SSO and integration users”

Reconnecting Salesforce requires the same OAuth pairing as initial setup:

  • The email you use to log into OutboundSync must match the Salesforce user who completes Connect.
  • You must be logged into Salesforce as that user in the same browser session when you click Connect.

If your org uses SSO (for example Okta), an integration user needs a working SSO login path. A password reset in Salesforce alone may not help when Okta manages credentials.

Symptoms of a user mismatch: OAuth loops, permission errors, or a connection that appears linked to the wrong Salesforce identity. If SSO blocks your integration user, reconnect with a human admin account. Created By on synced records will reflect whoever completes Connect — see Identifying OutboundSync activity in Salesforce.

After reconnecting

Section titled “After reconnecting”

Reconnecting OAuth alone does not repair webhook receivers tied to the old invalid token or user. Follow these steps:

  1. Create new webhook receivers — mirror the settings from your existing webhooks (platform, owner, object type, field mappings).
  2. Update Sales Engagement Platform URLs — copy each new webhook URL into your SEP:
  3. Confirm sync — send a test payload or trigger a live event and verify activity in Salesforce.
  4. Delete old webhooks (optional) — after the new webhooks are working, remove superseded receivers in OutboundSync.
  5. Replay held events — if sync was down for days or weeks, contact service@outboundsync.com to replay failed or held webhook events from the outage period.

OutboundSync may redirect you back to Connected Accounts without showing a clear connected confirmation. If you are unsure whether the reconnect worked, contact service@outboundsync.com with your OutboundSync account email and Salesforce domain. Our team can verify the connection on our end.

Section titled “Related guides”