Reconnect an expired or broken app connection

Connected apps can stop working when their access expires or is revoked. When that happens, any workflow that uses the app fails until you reconnect it. Here's how to spot an expired connection and refresh it.

How to tell a connection has expired

Each app you link is stored as a connected account with a status. A healthy account shows as active; one that needs your attention shows as Expired. This usually happens because the app revoked access, a password changed, or the access token timed out.

You'll most often notice it when a workflow stops working. A step or trigger that calls an app with an expired connection can't authenticate, so it fails and the run halts at that step.

Check your linked accounts under Settings, and review the affected automation in Workflows to see which step is stalled.

Reconnect the app

Reconnecting re-runs the same connect flow you used originally. It refreshes your user-owned account so the app can authenticate again — you don't need to rebuild the workflow.

1. Open the app's connection

   Go to the app in Settings, or open the workflow step that uses it in Workflows.

2. Start the connect flow again

   Choose Reconnect (or Connect). SAMI OS generates a fresh connect link and hands you off to the app to sign in.

3. Authorize access

   Sign in to the app and approve the requested permissions. When you return, the account status flips back to active.

4. Re-run the workflow

   Open the stalled automation in Workflows and re-run or re-enroll the affected contact so the failed step completes.

Reauthorize vs. SAMI-managed setup

There are two reasons a connection can break, and they're fixed differently:

• Needs reauthorization. Most apps use your own connected account. If the account expired, the reconnect flow above is all you need — you sign in and approve access again.
• Needs a SAMI-managed auth config. A few apps — including Follow Up Boss and GoHighLevel — require a SAMI-managed auth config in addition to your connected account. If that config isn't in place, the connect flow can't even start, and you'll see a message about a missing or invalid auth config rather than a normal expired status.

If reconnecting an ordinary app fails, retry the sign-in. If Follow Up Boss or GoHighLevel won't connect and reports an auth config problem, that's the SAMI-managed setup — reach out to your administrator or SAMI support to get the auth config provisioned, then connect your account.

You can also link apps directly while building an automation. See Workflows for connecting an app as part of a step.

Related articles

• Manage and switch between connected accounts
• Connect an app to SAMI OS
• Use a connected app as a workflow action