> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Gmail > Search and attach Gmail threads in Hebno, and send emails from a confirmation card after you review them. The Gmail integration adds the email history behind a client engagement to your work. Ask what Priya at Contoso last said about the renewal, attach a thread to a message, or have Hebno draft the follow-up. Hebno reads your mailbox with your own Google permissions and sends an email only when you select **Send** on the card. ## At a glance | | | | - | - | | **Connection** | Personal. Each member connects their own Google account. | | **Default access** | Read and write. Sending is a second grant, **Allow sending**, that you approve yourself. | | **Attach** | A message from your latest mail, or from a search | | **Search** | Hebno searches your mailbox when a request mentions a client, person, domain, topic or an earlier email | | **Link** | Not applicable. Gmail does not link to projects. | | **Write** | Send an email. Every send needs you to select **Send**. | ## Before you start You need a Google account with Gmail. If your Workspace restricts Gmail for third-party apps, a super admin must mark Hebno as trusted first. See [Google Workspace admin](https://hebno.com/docs/integrations/google-workspace-admin.md). ### Permissions | Scope | Why Hebno needs it | | - | - | | `https://www.googleapis.com/auth/gmail.readonly` | Search and read messages and threads. Granted when you connect Gmail. | | `https://www.googleapis.com/auth/gmail.send` | Send an email you confirmed. Granted only when you select **Allow sending**. | Hebno does not request permission to delete, label, archive or modify messages. ## Connect Gmail **1. Open Connections** Go to **Settings → Connections** and find **Gmail** under **Mail**. Or type `/` in the composer, choose **Gmail** and select **Connect**. **2. Approve read access** Select **Connect** (or **Grant access** if you already connected another Google product), sign in to Google and approve reading your mail. **3. Allow sending, if you want it** Select **Allow sending** on the Gmail row and approve the send permission. Without it, Hebno can draft an email but cannot send it. Because Google products share one connection, connecting Gmail does not request Drive, Calendar or Meet permissions. ### Enable for the organisation An owner or admin can select **Enable for the organisation** on the **Gmail** card under **Admin → Connectors → Catalogue**. A Workspace super admin approves the read permission for the domain, and members connect without a Google consent screen. Sending remains a personal grant each member chooses. See [Google Workspace admin](https://hebno.com/docs/integrations/google-workspace-admin.md). ## What Hebno reads | Gmail object | Fields Hebno uses | Typical questions | | - | - | - | | **Message** | Subject, From, To, Cc, date, body as plain text | "What did Priya say about the renewal terms?" | | **Thread** | The latest message with the earlier messages it quotes | "Summarise the thread with Contoso procurement." | | **Search results** | Subject, sender, date, link, an excerpt with the most relevant passages | "Find our emails with contoso.com since September." | When you attach a message, it becomes a Markdown file named after the subject, with the headers and body as plain text. Attachments on the email are not included. Hebno searches with Gmail's own search syntax. Name a person or domain, or use operators such as `from:priya@contoso.com`, `subject:"renewal"`, `has:attachment` or `after:2026/09/01`. Hebno returns one result per thread and reads up to five threads in chat and six in a research run. Reads are live: Hebno searches Gmail when a request needs it, and only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts from your email that a reply uses become part of the conversation. Anyone you share the conversation with can read them. Check a conversation before you share it. ## What Hebno writes Hebno drafts the email and shows a card titled **Email**. Edit any field, then select **Send**. **Dismiss** discards it. | Action | Gmail object | Fields on the card | | - | - | - | | **Send an email** | Message in your Sent mail | To, Subject, Message | ![Confirmation card for Gmail with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-gmail.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=e4f85fdfb07d5a5be9b2e7c4551d9494) A Gmail change pending confirmation. Nothing is written until you confirm. Recipients must be email addresses. If you name a person, Hebno matches the name to an address from your Google directory contacts when Google Calendar is connected, swaps the address in, and you check it before sending. The body is plain text. Files are not attached to the email, and the reply notes this when the deliverable is separate. The sent email appears in your Sent mail as you. Hebno never sends, replies, forwards, deletes or labels email on its own, and never changes drafts you created in Gmail. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Gmail You->>Hebno: Email Priya the revised timeline Hebno->>Gmail: Search recent threads with Priya Gmail-->>Hebno: Latest thread and her address Hebno-->>You: Email card with To, Subject, Message You->>Hebno: Edit and select Send Hebno->>Gmail: Send as you Gmail-->>Hebno: Message sent Hebno-->>You: Email sent to Priya ``` ## Use Gmail in chat * **Attach**: open the **+** menu, choose **Sources → Gmail**, and pick a recent message or type to search. Or type `/` and choose **Gmail**. * **Ask**: name the client, person or topic. For example: > What has Contoso procurement asked us to change in the master services agreement? > Summarise every email with contoso.com since the kickoff and list open questions. > Draft a reply to Priya confirming the revised workshop dates. * **Research runs** show a **Reviewing Gmail** step, with a chip for each thread. * **Agents** can read mail on a schedule, for example a Friday digest of client threads awaiting a reply. An agent cannot send. Any email it proposes appears in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md). ## Troubleshooting | Symptom | Fix | | - | - | | **Allow sending** appears on the row | Gmail is connected for reading only. Select **Allow sending** to approve the send permission. | | **Gmail can read mail but cannot send yet** | Select **Allow sending**, then select **Send** on the card again. | | A recipient is rejected | Use a full email address, or connect Google Calendar so Hebno can match a name from your directory. | | **No email matched** | Broaden the search or name the person. Gmail does not expand aliases in `from:`. | | Connecting fails with an admin message from Google | Your Workspace restricts Gmail for third-party apps. Ask a super admin to trust Hebno. | | **Unavailable** on the row | An admin blocked the integration. Ask an owner or admin to allow it under **Admin → Connectors → Catalogue**. | ## Related * [Google Workspace](https://hebno.com/docs/integrations/google-workspace.md) * [Google Workspace admin](https://hebno.com/docs/integrations/google-workspace-admin.md) * [Outlook](https://hebno.com/docs/integrations/outlook.md) * [Emails and invitations](https://hebno.com/docs/deliverables/emails-and-invitations.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.