Integrations
Google Workspace
Connect Gmail, Google Calendar, and Google Drive as source-first context — reads first; outbound mail stays approval-gated.
Google Workspace is one integration category with independently truthful rows for Gmail, Google Calendar, Google Drive, and Google Meet. Connecting Workspace does not mean every service is fully seeded, watched, or writable. Connect ≠ watch ≠ Brain ≠ writeback.
Meet has its own capture path (transcripts + notetakers) — see Google Meet. This page covers mail, calendar, and Drive as day-to-day context sources.
Fastest first win
If customers live in your inbox, connect Gmail early. Slack is still the fastest team-chat Brain light-up; Gmail is best when external signal lives in email. See Get your first win.
What you get
| Surface | Behavior |
|---|---|
| Gmail | Searchable discussion context; threads and signals can feed the Brain and tasks |
| Google Calendar | Read schedule context (prep, “who’s free,” meeting awareness) — read-first |
| Google Drive | Durable files can seed Brain content after connect (exportable text / supported types) |
| Google Meet | Transcripts via Drive or a notetaker — Meet guide |
HiveBase does not replace Gmail, Calendar, or Drive as products. It adds source-backed company context and governed actions on top.
Connect Google Workspace
Open Data Sources
In HiveBase, go to Settings → Integrations → Data Sources (or the setup Sources step during onboarding).
Connect Google Workspace
Choose Google Workspace and complete Google’s OAuth consent for the Google account you intend to use. Workspace admins may need to allow the app for your org.
Confirm services
Gmail, Calendar, Drive, and Meet are independent. A Drive extraction issue must not be treated as “Gmail is broken.” Reconnect or fix the service that actually needs attention.
Let context build
After authorize, HiveBase can search mail, read calendar, and seed Drive material into the Brain according to each service’s contract. Connecting alone is not a bulk “export my entire company” promise.
Gmail — source-first mail
Gmail is treated as a discussion source (same semantic family as Slack threads for “what did we discuss with this customer?”).
| Capability | Current posture |
|---|---|
| Read / search | Authorized mailbox context for search, triage, and Brain signals |
| Task evidence | Threads can attach to tasks as evidence when captured |
| Private vs workspace | Inbox content defaults toward private redaction scope; sent mail is workspace-shaped |
| Send / reply outbound | Approval-gated — agents draft; sending holds until you approve (or a category earns autonomy) |
Outbound email is a one-way door risk
Sending to a customer cannot be silently undone. HiveBase holds outbound mail at the approval boundary. See Trust & safety and Earned autonomy.
Calendar — read schedule context
Calendar is read-oriented for copilot and prep (“What’s on Thursday?”, attendee awareness). Creating or mutating events from agents is not the default first step — calendar write is a separate autonomy decision, not implied by connect.
Drive — durable files into the Brain
Drive connection can seed document-like material into the Brain (exportable text and supported types). Expect honest states for empty files, permission-denied items, and unsupported formats — not a fake “100% imported” progress bar.
What stays in Google
| Data or action | Current behavior |
|---|---|
| Full historical mailbox as a second Gmail UI | No — HiveBase is not a mail client replacement |
| Mail you never authorized / other users’ mail | Not accessible without their own connection / admin policy |
| Calendar event create/edit from agents | Not the default; read-first until you enable a governed write path |
| Silent bulk send | Never — outbound stays gated |
| Disconnect | Stops future access; revokes OAuth as designed; ledger history is not magically erased |
Disconnecting
From Settings → Integrations, open Google Workspace (or the specific service row) and disconnect / reconnect as needed. Future reads stop; tokens are revoked. Existing Brain claims and task evidence keep their history subject to workspace retention — same pattern as Slack.