Sign in to SALT

Connecting, disconnecting, and reauthorizing integrations

Connect by providing credentials and (where required) authorizing via OAuth. Disconnect to remove credentials; disable to keep them but pause sync. Reauthorize when "needs reauth" appears — credentials have expired or been revoked.

Updated Apr 29, 2026 • For agency admin

In short: Connect once per agency with credentials or OAuth. Disconnect removes the connection. Disable pauses without disconnecting. Reauth runs when “needs reauth” appears.

Connect an integration

  1. 1

    Open Integrations on your account.

  2. 2

    Pick the vendor.

  3. 3

    Click connect (or activate).

  4. 4

    Provide credentials, complete the OAuth flow, or enter the API key — depending on the vendor.

  5. 5

    Configure any vendor-specific settings (lead rules, default opportunity assignments, field mapping).

  6. 6

    Toggle on the Forms that should fire this integration.

  7. 7

    Test with a sample submission on one of the toggled Forms.

A successful connection moves the integration to enabled status. Unsuccessful connections stay in pending activation or unconfigured and surface an error message.

Disconnect

Disconnecting removes the credentials and stops all sync.

  1. 1

    Open the integration.

  2. 2

    Click disconnect (or deactivate).

  3. 3

    Confirm the prompt.

After disconnecting:

  • New Submissions don’t fire the integration
  • Pending async work (e.g. unfinished dec page requests) may still complete or fail naturally
  • Past synced records on the destination system are unaffected — disconnect doesn’t pull data back

To reconnect later, run the connect flow again. Some vendors require you to reauthorize from scratch; others remember your prior account.

Disable without disconnecting

If you want to pause sync temporarily — for example, while testing a new Form structure — disable without disconnecting:

  • Disable the integration toggle on specific Forms (no sync from those Forms only)
  • Or set the integration to disabled at the agency level (no sync from any Form)

Disabled integrations keep their credentials and configuration. Re-enabling resumes sync immediately.

Reauthorize (“needs reauth”)

When credentials expire (OAuth tokens age out, API keys are rotated, accounts are revoked), the integration’s status changes to needs reauth:

  • Sync stops on new Submissions
  • A header alert appears across your agency’s UI
  • The integrations dashboard flags the affected vendor

To reauthorize:

  1. 1

    Open the integration showing “needs reauth.”

  2. 2

    Click the reauthorize action.

  3. 3

    Re-complete the auth flow — re-enter credentials, complete OAuth handshake, or paste a refreshed API key.

  4. 4

    Sync resumes immediately.

If the reauth flow fails repeatedly, the underlying credential may be invalid or the vendor account locked. Contact the vendor’s support to verify the account before retrying.

Per-Form toggles

Connection is at the agency level; firing is per Form. After connecting:

  1. 1

    Open the Form you want to integrate.

  2. 2

    Open the Form’s integrations tab.

  3. 3

    Toggle on the integrations that should fire when this Form is submitted.

  4. 4

    Save.

A connected integration with no Forms toggled fires nothing — it’s connected but idle.

Common questions

Will disconnecting break my past sync history? No. Past synced records on the destination system stay where they are. Disconnect only stops future sync.

How long do OAuth credentials last? Depends on the vendor. AgencyZoom, for example, has had reauth events tied to its OAuth lifecycle. Most vendors refresh automatically when you use the integration; a multi-week gap can lead to expiry.

Why do some integrations say “pending activation” forever? Some vendors (notably Epic Quotes) require SALT staff to approve activation. Contact support if you’re stuck in that state.