Gmail

Connect Gmail so your agents can read inbound email and reason about correspondence. Common use cases include AP help desk, vendor inquiries, and remittance handling.

Audience: IT (the enabler) and builders

What it can do

  • Read. Mailbox sync.

This integration does not support Write, Triggers, or Reply through the workspace-level integration. The bound email pattern adds them on top.

Triggers and Reply come from binding. Want inbound mail to fire work items and the agent to reply through this mailbox? See Bound email for the full wiring with email templates.

Who connects this

Admin-enabled OAuth. IT sets up the Google Cloud project once. After that, builders OAuth their own mailbox.

IT sets up the Google Cloud project and OAuth client

Create the Google Cloud project, configure the OAuth client, and approve the required scopes.

Builders OAuth their own mailbox

Once stage 1 is done, builders OAuth from within the platform.

Builder picks a mailbox for the Project

In the Project context, pick the mailbox the Project should read.

What this article will cover

  • Setting up the Google Cloud project and OAuth client
  • Required scopes
  • Connecting and authorizing
  • Choosing a mailbox or shared mailbox
  • Verifying the connection
  • Common errors and how to resolve them