AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
Made in India
Skip to documentation
AtlasDocs
Back to Atlas

Start here

  • Overview

Developer

  • REST API
  • MCP (AI agents)
  • SDKs
  • Quick actions

Connect

  • Connectors
  • Integrations

Reference

  • Keyboard shortcuts
  • Module reference

GmailEmail

Pull threads, messages, and labels from a connected Gmail mailbox so you can triage email inside Atlas.

What this connector does

  • Pull individual mailbox threads, messages, and labels for the connected user.
  • Convert any thread into an Atlas task with the original email preserved as context.
  • Sync read state and starred state back to Gmail so the mailbox stays in sync.
  • Watch for new messages with a label-scoped poll so triage runs in near real time.

Before you begin

  • You are an admin in the Google Cloud project used for the OAuth client.
  • You can edit the Atlas tenant Integrations settings.
  • You have a sandbox Google account to validate the first connection before rolling out.

Get your credentials

1

Open the Google Cloud console

Sign in with an admin account that owns the Cloud project Atlas will use. console.cloud.google.com

Screenshot placeholder
2

Create an OAuth 2.0 Client ID

In APIs and Services, open Credentials, then create an OAuth client of type Web application. APIs and Services, Credentials

Screenshot placeholder
3

Add the Atlas redirect URL

In Authorized redirect URIs add https://YOUR-ATLAS-HOST/oauth/callback/gmail. Replace YOUR-ATLAS-HOST with the host serving Atlas.

Screenshot placeholder
4

Enable the Gmail API

In APIs and Services, Library, search for Gmail API and enable it for this project. Enable Gmail API

Screenshot placeholder
5

Copy the client id and secret

Open the OAuth client you created and copy both values. Paste them into the Atlas Gmail connector settings page and click Save.

Screenshot placeholder

Required scopes and permissions

Read messageshttps://www.googleapis.com/auth/gmail.readonly
Modify labels and read statehttps://www.googleapis.com/auth/gmail.modify
Account profileopenid email profile

Setup checklist

  1. Create the provider app in a sandbox or development workspace.
  2. Add the Atlas redirect URL to the provider app configuration.
  3. Copy the client id, client secret, or API key.
  4. Paste the credentials into the Atlas connector settings page.
  5. Click Connect and complete the provider sign-in screen.
  6. Run Test connection from the connector page to verify health.

Troubleshooting

  • redirect_uri_mismatch

    The redirect URI in the OAuth client must exactly match the one Atlas advertises, including https and trailing slash.

  • access_denied during consent

    Confirm the test user is added under OAuth consent screen, Test users, while the consent screen is still in Testing.

  • invalid_scope

    The Gmail API was not enabled on the project. Enable it in API Library and retry.

Webhooks

Gmail uses a polling watch rather than push webhooks. Atlas runs a labeled-sync poll on the connected mailbox.

Events Atlas listens for

  • New message in INBOX
  • Label added or removed
  • Message marked read or starred

Disconnect and data deletion

  1. Click Disconnect on the Atlas Gmail connector page to revoke the refresh token.
  2. Open https://myaccount.google.com/permissions and remove the Atlas app for the connected account.
  3. Atlas deletes the locally cached thread metadata for that user within 24 hours of disconnect.

Ready to connect Gmail?

Paste the credentials you copied above into the live connector page.

Open the connector page