AtlasWork, planned itself.

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

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

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

    Resources

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

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
    PrivacyTermsSecurityStatus

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • Necessaryalways on
    • Analyticsopt-in
    • Marketingopt-in
    • Preferencesopt-in
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

    • REST API guide
    • Authentication
    • API reference
    • MCP (AI agents)
    • MCP tools reference
    • SDKs
    • Quick actions
    • Changelog

    Webhooks

    • Overview
    • Quickstart
    • Events
    • Payloads and headers
    • Security and signing
    • Delivery and retries
    • Managing via API

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Gmail logo

    Email

    Gmail

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

    AuthOAuth 2.0UpdatesPollingAvailable

    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

    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

    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.

    4

    Enable the Gmail API

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

    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.

    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.

    Once you have the credentials above, paste them into the live connector page to finish connecting Gmail.

    Open the Gmail connector page

    On this page

    • What this connector does
    • Before you begin
    • Get your credentials
    • Required scopes and permissions
    • Setup checklist
    • Troubleshooting
    • Webhooks
    • Disconnect and data deletion