MeetbookMeetbook Help

An integration disconnected itself — why?

Token expiry, revoked OAuth scope, re-auth steps.

Every integration lives on Settings → Integrations — Airtable, Google Calendar, Google Docs, Google Drive, HubSpot, Jira, Notion, Outlook Calendar, Salesforce, and Slack.

Integrations grid with Connect buttons for each supported app

If one that was working suddenly shows as disconnected, it's almost always one of these:

The access token expired or was revoked

OAuth tokens can be revoked by the other side — the connected app's admin, an IT policy, or the provider itself after a long period of inactivity. Meetbook can't refresh a token that's been revoked upstream; you'll need to reconnect.

The account that connected it left, or lost access

Integrations are tied to whichever account authorized them. If that person's access to the third-party app (Slack workspace, Notion workspace, Salesforce org) was removed, the connection breaks from that side.

A password or 2FA change on the connected account

Some providers invalidate existing app authorizations when the account's login credentials change. Reconnecting re-establishes it.

Fixing it

Go to Settings → Integrations, find the disconnected app, and click Connect again — this re-runs the same authorization flow as the first time. Nothing already delivered through the integration is lost; only new meetings going forward are affected until it's reconnected.

On this page