Gmail is part of Customer intelligence, a paid add-on. Contact the Hyperline team through the in-app chat to enable it.
Gmail is user-scoped: each teammate connects their own mailbox from Profile > Integrations, not from the workspace-level Settings > Integrations page. Hyperline only sees the mailboxes of the users who connected.
Prerequisites
A Google account with the mailbox you want Hyperline to read.Connect Gmail
1
In Hyperline, open Profile > Integrations
2
Click Connect on Gmail
3
Choose your Google account and review the requested access
4
Confirm
You are redirected back to Hyperline and the connection appears as active for your user.
Requested permissions
Hyperline requests read-only access to Gmail, plus your basic profile information to identify the connected account. The connection never sends, replies to, deletes, or modifies anything in your mailbox.What Hyperline fetches
Hyperline never reads your whole mailbox. It searches Gmail once per customer domain, for messages sent to or received from that domain, and keeps only the results that match a known customer. For every matched email, Hyperline stores:
Emails that do not match a customer domain are discarded and never stored.
Synchronization
Hyperline synchronizes mailboxes once a day, for every user who connected their Google account. The recurring run looks one day back, so it only picks up new messages. A full-history search runs instead when the sync is scoped to a single domain, for example when a customer is created. That search is capped per domain, so a very large history is not retrieved in full.Where Gmail data appears
- Customer page: the Integrations section shows a Gmail row with the most recent email. Open it to browse synced threads and their content.
- Monitoring agent: email is handled separately from the other connectors. When Gmail is connected for users in your workspace, the agent can use recent customer email threads without a toggle in the agent’s Connectors tab.
- Analysis results: Gmail appears under Data sources when email context was used.

