Connecting Gmail and Google Drive
Connect Gmail and Google Drive from the Account section of Settings — each is a toggle row that walks you through a one-time Google sign-in. Gmail powers inbox automations, Gmail draft composing, and Google Calendar features; Drive powers folder-watch import automations. Connecting either requires a Pro plan.
Document Blueprint's integrations are personal: you connect your own Google account, and everything that runs on that connection — automations you create, drafts you compose, calendar events you add — runs under your credentials. Tokens are never shared between teammates, so each member who wants to power automations or compose drafts connects their own Gmail.
What you need
- A Pro workspace plan. Toggling a connection on a Free or Lite plan shows "The active workspace requires a Pro subscription to connect automations."
- A Google account you're willing to grant access from. For Gmail you'll also be granting Google Calendar access in the same consent screen.
Where integrations live
Open Settings and select Account (the Settings sidebar groups Preferences and Account under "You"). Below the Plan row you'll find two integration rows:
- Gmail — a toggle switch with the row subtitle showing either
Not connectedor the email address of the connected Google account. - Drive — the same pattern for Google Drive.
What each connection powers
| Connection | Powers |
|---|---|
| Gmail | Inbox automations (subject/sender filters that ingest email attachments into cases), composing Gmail drafts when you share a case, and Google Calendar features — the consent screen requests calendar access alongside Gmail, so "Add to Google Calendar" on case dates and the chat's calendar tools ride on the same connection. |
| Drive | Drive import automations — watch a Drive folder and pull new files into the intake pipeline — plus the File storage option on automations that keeps ingested copies in Drive (Firebase / Google Drive / Both). |
Two distinctions worth keeping straight:
- Connecting Gmail does not let Document Blueprint send email. Sharing a case creates a real draft in your Gmail mailbox; you review it and click Send inside Gmail yourself.
- An automation runs under the Google account of whoever created it (the "powering user"), not the workspace owner's.
The connection flow
That's the whole flow. The consent screen is standard Google OAuth: Gmail asks for mailbox read/modify access plus calendar access; Drive asks for read access to your Drive files. Once connected, the row's subtitle switches from Not connected to your account email.
When access is revoked
Google access tokens can stop working — you revoked the app from your Google account settings, your organization rotated credentials, or the grant expired. When that happens, every automation powered by your account pauses automatically rather than failing silently. The automation's card shows an amber banner with the reason:
OAuth expired — reconnect Gmail— your Gmail grant stopped working.OAuth expired — reconnect Drive— your Drive grant stopped working.Connected user removed from workspace— the teammate whose account powered the automation was deactivated; a workspace owner can delete these orphaned automations or recreate them under another account.Paused manually— someone clicked Disable; not an access problem.
To recover from an OAuth pause: go back to Settings → Account, toggle the affected integration on again, and complete the Google consent screen. Then re-enable the paused automations from the Automations drawer.
Disconnecting
Toggle the row off. Disconnecting revokes the token with Google and deletes the stored credentials; for Drive it also stops any active folder watch. Automations powered by your account will stop ingesting until you reconnect, and you won't be able to compose Gmail drafts or add calendar events until Gmail is connected again. Your existing cases, files, and extracted data are untouched.