Help Center
Connectors

How do I fix a connector that shows "Relink Needed"?

Updated 4 days ago

Relink the existing connector with Relink Connector on the connector's page. Your customer re-enters their credentials, and the connector keeps its connector token, its sync history and every Bindbee ID you've stored.

Relink Needed means your customer's credentials in their HR system expired, were changed, or lost access. Syncing stops until the connector is relinked, but your API reads keep returning the data from the last successful sync.

  1. Open Connectors and select the connector. It shows a Relink Needed banner with the date it entered that state.

  2. Click Relink Connector.

  3. Choose how to relink:

    • Re-generate Magic Link creates a new link for the same connector. Send it to your customer's HR system admin, with the setup guide for their integration from help.bindbee.dev.

    • Update Credentials lets you enter new credentials directly, if your customer has already given them to you.

  4. After the connector is relinked, click Force Sync instead of waiting for the next scheduled sync.

  5. Check that the new sync completes on the connector's Sync tab.

If a token, certificate or integration user was rotated on your customer's side, they need the new values ready before they open the link. Magic Links expire 7 days after they're created.

Don't delete the connector and create a new one. A new connector gives every record a new Bindbee ID, so every ID you've stored stops matching.

Relinking from your own product

You can't start a relink through the API. To keep the delay short, watch for the problem, then generate the relink link from the dashboard:

  • Check the status field from Get Connectors for RELINK_NEEDED.

  • Or subscribe to the connector_sync_error webhook and check connector.connector_status in the payload.

Troubleshooting

Cause: the new credentials are valid but don't have the access the sync needs. Fix: read the failed model's error on the Sync tab and ask your customer to grant the missing permission.

Several connectors for the same integration need relinking at once

Cause: usually an outage or change on the provider's side rather than each customer's credentials. Fix: relink one connector first. If it still fails after your customer reauthorizes, contact us and we'll investigate before you contact the others.

Cause: the connection might use a personal account that's affected by password rotation or offboarding. Fix: ask your customer to connect with a dedicated integration or service account.

Was this helpful?
Was this helpful?