Short answer
AI connects to Google Workspace through Gemini, which is included in Business and Enterprise plans, through the Gmail, Drive and Calendar APIs, or through Google’s Workspace MCP servers, in developer preview since May 2026. For New Zealand businesses a strong first project is shared inbox triage: the AI labels each email and writes a reply draft, and staff edit and send it.
- Gemini is included in Workspace Business plans; Business Standard is NZ$21 a user a month.
- Gmail’s readonly, compose and modify scopes are restricted and need Google verification for public apps.
- Internal apps owned by your organisation skip verification and the 100-user cap.
- Gmail push notifications must be renewed at least every seven days.
- Google plans to charge for Gmail API use beyond quota later in 2026.
What Google’s built-in AI does today
Since 16 January 2025 Google has included Gemini in Workspace Business and Enterprise plans rather than selling it as an add-on. On 19 October 2026 Google’s NZ pricing page listed Business Starter at NZ$10.50, Business Standard at NZ$21 and Business Plus at NZ$33 per user per month (Workspace pricing). On Starter, Gemini works in Gmail only; Docs, Sheets and Slides start at Business Standard. Google’s AI page also lists the Gemini app, Gemini Notebook (formerly NotebookLM), Workspace Intelligence across Gmail, Docs, Sheets and Meet, and Studio for AI workflows. Google says customer content is not used to train generative models outside your domain without permission.
Gemini helps an individual write a reply. It does not give a shared inbox consistent labels, routing rules and an audit trail. That is what an integration adds.
Integration routes and when to use each
| Route | What it gives you | Use it when |
|---|---|---|
| Gemini in Gmail | Summaries and drafting for the signed-in user | Individuals handling their own mail |
| Studio | Google’s own AI workflows across Workspace apps | Simple flows staff can build themselves |
| Gmail API | Read, label and draft under your rules | A shared inbox with fixed categories and logging |
| Gmail push notifications | Cloud Pub/Sub message when a mailbox changes | Near real-time triage without constant polling |
| Workspace MCP servers | Per-product MCP endpoints (Gmail, Drive, Calendar and others) that inherit the user’s permissions | Trials with MCP clients; developer preview only |
| n8n, Make or Zapier | Gmail triggers plus an AI step | Low volume, one mailbox, simple labels |
The Workspace MCP servers need membership of Google’s Developer Preview Program (setup guide), so do not build production processes on them yet. See MCP for business systems for how they fit later.
Automation 1: shared inbox triage
- Inputs
- New mail in a shared mailbox such as accounts@ or bookings@.
- Trigger
- Gmail push via Pub/Sub, then history.list from the last saved historyId to find new messages.
- Model step
- Classify the latest message (not the quoted history) into one of six to eight fixed labels, with a confidence score, and extract the customer’s reference number and requested date.
- Checks in code
- The label must be on the allowed list; references must match your system’s format.
- Write-back
- Apply the Gmail label and an “AI processed” label; anything below the confidence threshold gets “Needs triage”.
- Human review
- The inbox owner checks “Needs triage” daily and a sample of confident labels weekly.
Automation 2: reply drafts staff approve
- Read. For labels that need a reply, read the thread and the matching policy or price list from a named Drive folder.
- Draft. The model writes a reply in your house style, citing the policy it used in an internal comment to the reviewer.
- Save as draft. Create a Gmail draft in the same thread and label it “AI draft”. The agent never holds send permission.
- Approve. Staff open Drafts, edit and send. Track how much each draft is changed to see which categories are ready for less review.
Field mapping matters more than it looks. A draft only lands in the right conversation if it carries the original threadId, a matching subject, and In-Reply-To and References headers taken from the original Message-ID. Store the historyId after each run as your checkpoint, and skip any message already labelled “AI processed” so retries do not double-draft. Our lesson on drafting emails with human review covers the reviewer side.
Permissions, scopes and approval design
Google classes gmail.readonly, gmail.compose and gmail.modify as restricted, gmail.send as sensitive and gmail.labels as non-sensitive (Gmail scopes, updated 10 September 2026). Split services by scope: the classifier needs read and modify (to apply labels), the drafter needs compose, and nothing needs send. Public apps that store or transmit restricted-scope data must pass a security assessment. An internal app, used only within your Workspace organisation, with an organisation-owned project and an internal consent screen, does not need verification (Google Cloud Help). Avoid domain-wide delegation for one shared mailbox, because it lets a service account act as any user for its granted scopes.
Costs and limits
Gmail allows 1,200,000 quota units per minute per project and 6,000 per minute per user, and Google says usage beyond quota “is planned to incur charges” later in 2026 (Gmail quota, updated 16 October 2026). Model costs are small. Illustrative example: 3,000 emails a month classified on Claude Haiku 5.5 (2,000 input and 100 output tokens each, at US$0.10 and US$0.50 per million) costs under US$1. Drafting 1,000 replies on Claude Sonnet 5.5 (6,000 input and 500 output tokens, US$2 and US$10 per million) adds about US$17. Prices as listed on 19 October 2026. Do not use the free Gemini API tier for customer mail: Google’s terms say free-tier content may be used to improve its products and tell users not to submit personal information (Gemini API terms).
Where it goes wrong
- Missed notifications. Google says push notifications can be delayed or dropped, and a watch lapses unless renewed at least every seven days (push guide). Renew daily and run history.list hourly as a safety net.
- Instructions inside emails. An inbound email can contain text aimed at your model. Drafts-only access limits the damage; test with the cases in our prompt injection testing guide.
- Forwarded chains. Classify the newest message, not the thread, or a reply to an old complaint is filed as a complaint.
- Privacy. Customer emails are personal information under the Privacy Act 2020. Use paid model services that process on your behalf, and keep logs only as long as you need them.
- Manual recovery. Labels and drafts are reversible. Add a “Reprocess” label staff can apply to send a message back through the pipeline after a fix.
For documents in Drive, see AI and Google Drive. For the wider picture of Gemini, see our Gemini guide, and for building and running the pipeline, our AI workflow automation service.
Sources
- AI in Google Workspace, Google, accessed 19 October 2026
- Google Workspace pricing (NZ), Google, accessed 19 October 2026
- Generative AI in Google Workspace Privacy Hub, Google Workspace Admin Help, updated 6 October 2026
- Choose Gmail API scopes, Google for Developers, updated 10 September 2026
- Push notifications, Google for Developers, updated 15 September 2026
- Gmail API usage limits, Google for Developers, updated 16 October 2026
- Configure the Google Workspace MCP servers, Google for Developers, updated 13 October 2026
- Agent tools and security updates for Workspace developers, Google Workspace Updates, 1 May 2026
- When is verification not needed, Google Cloud Help, accessed 20 October 2026
- Gemini API Additional Terms of Service, Google, effective 23 March 2026
Written by the Levy Street team in Wellington. Last updated 19 October 2026.