Gmail

• 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.

• 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.

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.

• 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.

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

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.