What you get
- Gmail message metadata and Google Calendar events update the relationship graph continuously
- Pre-meeting briefings for Google Calendar events — attendees, last contact, related insights
- Detect contacts going quiet from Gmail activity, not CRM activity
- Admin-scoped install: one domain admin authorizes, all users benefit without individual OAuth
How it works
Bionicly is installed by a Google Workspace super-admin as a domain-wide OAuth 2.0 application. Scopes are metadata-only (gmail.metadata, calendar.readonly) — Bionicly cannot read message bodies without an additional per-user opt-in.
Our connector reads Gmail message metadata (sender, recipient, subject, timestamp, labels) and Google Calendar event metadata via the Google Workspace APIs.
Signals join the same relationship graph as Microsoft 365 and Salesforce. Bionicly's insights are delivered via email, the Bionicly UI, or a scheduled Slack/Teams digest.
Data flows
Data flow
Google Workspace
System of record
Reads
Writes back
Reads
- Gmail message metadata (gmail.metadata scope — no body content)
- Google Calendar event metadata (calendar.readonly)
Writes back
- Optional: Google Calendar event annotations, opt-in per user
Metadata and derived insights only. Message bodies are never read unless a user explicitly opts into full-text analysis.
Reads
- Gmail message metadata (gmail.metadata scope — no body content)
- Google Calendar event metadata (calendar.readonly)
- Google Workspace directory (user + group listings for scoping)
Writes
- Optional: Google Calendar event annotations, opt-in per user
Storage
Metadata and derived insights only. Message bodies are never read unless a user explicitly opts into full-text analysis.