SAMIOS
Help Center

Sync CINC webhooks and fix connection errors

Keep CINC webhooks live, re-register them after a sync drops, and fix common CINC connection errors in SAMI OS.

Open in SAMI OS

Once your CINC account is connected, SAMI relies on a live webhook to receive new leads and updates the moment CINC sends them. This article shows how to read the webhook status on a connected account, re-register it when it drops, and resolve the connection errors you might see along the way.

Check webhook status

Open Settings and select the CINC tab to see every CINC account you've connected. Each account shows a status badge next to its name:

  • Webhook live — CINC is registered to push events to SAMI. Nothing to do.
  • Needs sync — the webhook isn't confirmed, so inbound CINC events may not reach SAMI until you re-register it.

Below each account, Webhook activity shows when SAMI last received an event from CINC, or No events yet if none have arrived. If a recent sync failed, the error text appears in red right under the account details.

CINC connections are personal — each agent owns their own connection, and agents don't inherit a broker's CINC access. You'll only see and manage the accounts you connected yourself.

Re-register the webhook

If an account reads Needs sync, or you saw the warning that OAuth succeeded but the webhook couldn't be confirmed on the first pass, re-register it with one click.

  1. Open the CINC tab

    Go to Settings and open the CINC tab to find the connected account.

  2. Click Sync webhook

    On the account, click Sync webhook. SAMI re-registers the webhook with CINC using your connected token.

  3. Confirm it's live

    When it succeeds, the badge flips to Webhook live. If it fails, the error message appears under the account so you know what to fix.

If syncing returns a message that CINC rejected webhook registration for this user or token, the connected CINC login may lack permission to authorize the requested access. Have that user confirm their CINC access, then sync again — or disconnect and reconnect.

Fix CINC connection errors

If a connect attempt fails, SAMI returns you to the CINC tab with a "CINC authentication failed" banner and a specific message. Match yours below:

  • CINC rejected the authorization request (provider error) — verify the CINC site domain you entered, and that the CINC user can authorize the requested access.
  • Token exchange failed — CINC returned a code but SAMI couldn't trade it for tokens. The registered redirect URI or app credentials need to be verified with CINC.
  • Account setup failed — CINC returned tokens, but SAMI couldn't finish setting up the connected account. Retry the connect flow.
  • Invalid state — SAMI couldn't validate the OAuth state. Start a fresh connect flow and finish it in the same browser session, without switching browsers or windows.
  • Missing code — CINC redirected back without an authorization code. Retry the connect from the CINC tab.

The banner may include a CINC debug ID. Keep it handy if you contact support — it helps trace the exact attempt.

Disconnect an account

To remove a CINC connection, click Disconnect on the account, then confirm. Any workflow or Zapier bridge that used that account's connection ID will stop working until you reconnect. You can manage the rest of your automations from Workflows after disconnecting.

Related articles

Last updated 2026-06-21

Was this helpful?