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
    Google Drive logo

    Storage

    Google Drive

    Index Google Drive folder and file metadata so contracts and evidence files can be linked into Atlas records.

    AuthOAuth 2.0UpdatesReal-timeAvailable

    What this connector does

    • List shared drives and folders the connected user can access.
    • Index file metadata (name, owner, modified time, mime type) for searchable evidence links.
    • Attach Drive file links to tasks, deals, and contracts without copying file content.
    • Optionally watch a folder so newly added files appear in Atlas evidence references.

    Before you begin

    • You are an admin in the Google Cloud project used for the OAuth client.
    • The Google Workspace admin allows third-party access to Drive metadata.
    • You have a sandbox folder for first validation before rolling out to the workspace.

    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, Credentials, create an OAuth client of type Web application.

    3

    Add the Atlas redirect URL

    In Authorized redirect URIs add https://YOUR-ATLAS-HOST/oauth/callback/google-drive.

    4

    Enable the Google Drive API

    In API Library, search for Google Drive API and enable it for the project. Enable Google Drive API

    5

    Copy the client id and secret

    Open the OAuth client and copy both values. Paste them into the Atlas Google Drive connector settings page and click Save.

    Required scopes and permissions

    Read file metadatahttps://www.googleapis.com/auth/drive.metadata.readonly
    Read file content when explicitly requestedhttps://www.googleapis.com/auth/drive.readonly
    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

    • access_denied during consent

      Confirm the user is listed under OAuth consent screen, Test users while the screen is in Testing mode.

    • insufficient permissions on a folder

      The connected user must have Viewer or higher on the folder. Re-share and retry.

    • invalid_scope

      The Drive API was not enabled in this Cloud project. Open API Library and enable it.

    Webhooks

    Atlas uses Drive watch channels to receive change notifications. Channels expire and Atlas renews them automatically.

    Events Atlas listens for

    • File created in a watched folder
    • File renamed or moved
    • File trashed

    Provider docs: https://developers.google.com/drive/api/guides/push

    Disconnect and data deletion

    1. Click Disconnect on the Atlas Google Drive 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 removes cached file 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 Google Drive.

    Open the Google Drive 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