Help Center

An Integration Needs Reconnecting

Open your dashboard, go to Integrations, and use the Reauthorize or Reconnect button on the integration that’s flagged. That’s the whole fix — it takes you back through the provider’s sign-in and clears the alert.

Two different messages

“Reauthorization required” is a warning shot. The connection to one of your lock accounts is about to lapse, usually because a token expired or the provider changed something. Your automation is still running. Reconnecting now avoids an interruption.

“Integration disconnected” means it already lapsed, and automation is paused for that connection. New codes won’t be generated for upcoming bookings and booking changes won’t sync until you reconnect.

What keeps working while it’s disconnected

Codes already programmed on your locks stay on them. Guests currently in your properties, and guests whose codes were already written, can still get in.

What stops is everything forward-looking: new bookings won’t get codes, changed dates won’t reschedule, and cancellations won’t clear codes off the lock. That last one is the one to watch — a cancelled guest can keep working access until you reconnect and the cancellation syncs.

After you reconnect

Check upcoming bookings for the affected properties. Anything that was created or changed during the outage needs its code to exist — reconnecting resumes automation going forward but you should confirm the near-term arrivals rather than assume the backlog resolved itself.

If a booking that should have a code doesn’t, reapply it from the booking.

The reconnect button in the notification email currently points at a page that doesn’t exist, so it lands on a not-found screen. Ignore it and go to your dashboard’s Integrations section directly — that’s where the working button lives. We’re fixing the link.