Google Drive Integration Guide

Last updated: December 4, 2025

This article walks you through how to integrate Google Drive with Swyft AI, the permissions (scopes) required, and how user permissions are respected during setup. Swyft AI connects to Google Drive via OAuth, meaning a Google Workspace admin may need to approve the integration and grant the necessary scopes depending on your organization’s policies.

Overview

Swyft AI uses Google Drive APIs to create and manage Google Docs so your workflows can automatically generate documents such as call summaries, account plans, QBR templates, or handoff notes.

Important: Swyft AI cannot perform any actions in Google Drive that your Google Workspace admin or your own user account has not allowed. We do not override your organization’s Google Drive or Google Workspace security settings.

Required Scopes

When authorizing Swyft AI to connect to Google Drive, you will be prompted to grant the following scope:

  • https://www.googleapis.com/auth/drive.file
    Allows Swyft AI to create, open, and edit files in Google Drive that were created by Swyft AI or that you have explicitly opened with Swyft AI. It does not grant full access to all files in your Drive by default.

Google may also show standard profile related scopes such as basic account information, which are required by OAuth to associate the integration with your Google user, but the only Drive permission Swyft AI relies on is drive.file.

Why this scope?

  • Document Creation: Swyft AI needs the ability to create new Google Docs in your Drive so workflows can generate content (for example a meeting summary document) as part of an automated process.

  • Scoped File Access: The drive.file scope limits access to files that Swyft AI creates or that you explicitly use with the app, which aligns with least privilege and reduces risk compared to broader Drive scopes.

  • Editing and Updates: Workflows may need to update existing Swyft generated documents, append sections, or adjust content as customer data changes.

Setting Up the Integration

  1. Go to the Integrations Page in Swyft AI
    From your Swyft AI account, navigate to the Integrations section.

  2. Click “Connect” Next to Google Drive
    Select Google Drive from the list of available integrations and click “Connect.” This will open the Google OAuth permissions screen in a new window.

  3. Choose the Correct Google Account
    Select the Google Workspace or Gmail account that you want Swyft AI to use for creating and managing Google Docs.

  4. Review and Approve Scopes
    Review the requested permissions, including https://www.googleapis.com/auth/drive.file, then click “Allow” to grant access.

    1. In some organizations, a Google Workspace admin may need to pre approve or review the app before users can connect.

  5. After approval, Swyft AI can create and edit Google Docs using your Google Drive account, within the limits of the drive.file scope and your organization’s Google Workspace policies. No additional configuration is required inside Swyft AI.

Respecting Google Drive Permissions and Security

User Level Permissions

Swyft AI acts on your behalf in Google Drive. Any document creation or editing respects the permissions of the connected Google account. If you cannot access or modify a file in Drive, Swyft AI cannot either.

  • No Full Drive Access
    Using drive.file, Swyft AI can only access:

    • Files and folders it creates.

    • Files you open with Swyft AI or explicitly authorize through Google’s consent screen.
      It does not gain unrestricted access to every file or shared drive in your organization.

  • Revoking Access
    You can revoke Swyft AI’s access at any time from your Google Account security settings under “Third party access,” or your Google Workspace admin can revoke or restrict access for all users through the admin console.

If you have any further questions about setting up or managing your Google Drive integration, please reach out to our support team at hello@swyftai.com. Our team can help you verify scopes, review security implications, and ensure your workflows are creating Google Docs in the right place.