Connecting your Google Calendar lets Databook use your meetings to prepare you for customer conversations and to show your account team who you're actually engaging with. This article covers what the integration does and how to pick a connection method; see the linked guides for setup steps.
What it can do
Meeting briefings and debriefs: when you opt in, Databook detects your upcoming external meetings and prepares a brief 24 to 48 hours ahead of time. You then finish preparing the brief through a short 1 to 3 step guided flow. After the meeting, Databook prompts you to run a debrief to plan next steps, draft a follow-up email, and share actions with your team.
Relationship mapping across an account: by looking at who on your team is meeting with whom at a customer, Databook can build a map of the breadth and seniority of your engagement across an account, without you having to track it manually.
Choosing a connection method
There are two ways to connect Google Calendar. Which one fits depends on how many calendars need to sync and how much calendar-level control you want.
Dimension | OAuth | Workspace Delegation |
Authorization | Each user (or a shared integration account) logs in and approves access. | A Workspace super-admin authorizes access once for the whole domain. |
Private events | Only visible on calendars the integration account owns. On other shared calendars, private events show as "Busy" with no details. | Visible on every synced user's calendar, since the connection acts as that user. |
Scale | Best kept under roughly 400 subscribed calendars; performance degrades beyond that. | Scales to every user in a domain, one connection per user. |
Best for | Smaller deployments where you want calendar-level control over what Databook can see. | Large deployments syncing many users at once. |
See the detailed guides for setup steps and the trade-offs of each:
How we protect your privacy
Private events are captured on ingestion but filtered out before they're used anywhere else in the product, and cancelled meetings are removed the same way. This applies regardless of which connection method you use.