Skip to main content

Connecting to Google Workspace

Connect your Google Workspace email account to CX.

Written by Andrew Flowers
Updated today

This guide is specifically for connecting a Google Workspace (Gmail) mailbox to Stax.ai CX Inbox. It explains the Google OAuth connection flow, what sync data is brought into CX, how quickly data appears, what statuses mean, and how to troubleshoot common Google-specific issues.

Your Gmail mailbox remains the source of truth, while CX provides the workflow layer for viewing, organizing, and acting on email in context.

Google Workspace connection specifics

  • Connection flow is the same as other providers, but Google behavior is most affected by OAuth token lifecycle, Google Admin app policies, and multi-account session selection.

  • Authorization is account-specific (not domain-wide by default). If access is revoked by user or admin, CX moves to Disconnected until reauthorization.

Data CX syncs

  • Thread/message IDs, sender/recipient headers, subject, text/HTML body, timestamps, read state, and attachment metadata.

  • CX workflow metadata when used (for example bookmark/tags/importance/sentiment/safe-for-everyone and scheduled-send fields).

Sync timing and limits

  • Initial sync is newest-first historical ingestion.

  • Typical scope target: up to 6 months of history or up to 10,000 messages per selected folder/label (whichever hits first).

  • Ongoing sync is incremental; Re-Sync Messages can force an immediate refresh attempt.

Statuses

  • Connection: Connected, Syncing, Disconnected.

  • Delivery: Pending, Sent, Failed.

Google-focused troubleshooting

  • Wrong account connected: sign out of extra Google sessions, reconnect, and explicitly choose the correct mailbox.

  • Missing messages: verify selected folder/label scope, allow backfill time, then run Re-Sync Messages.

  • Disconnects: reconnect mailbox and confirm Google Admin has not restricted/revoked access.

  • Delayed or failed sends: check connection state and Outbox Failed items, then retry after reconnecting if needed.

Did this answer your question?