> ## Documentation Index
> Fetch the complete documentation index at: https://atmet.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Drive Integration: Automate Your File Workflows

> Connect Google Drive to Atmet to trigger workflows on file changes, upload documents, manage folders, and automate your entire file lifecycle.

The Google Drive integration brings your cloud file system into Atmet workflows. You can start automations the moment a file is created or changed in Drive, then chain actions to copy, move, share, or delete that file — or pass its contents downstream to other tools. Whether you're building a document approval pipeline, auto-organizing a shared team Drive, or generating reports that land in the right folder automatically, this integration gives Atmet full read and write access to your Drive environment.

## Prerequisites

Before connecting Google Drive, make sure you have:

* A Google account with access to Google Drive
* Permission to grant third-party OAuth access (check with your Google Workspace administrator if you're on a managed account)
* For shared drive use cases: Contributor or higher access to the relevant shared drives

***

## Connecting Google Drive

<Steps>
  <Step title="Open Integrations">
    In the Atmet sidebar, navigate to **Integrations** and find **Google Drive** in the list.
  </Step>

  <Step title="Click Connect">
    Click the **Connect** button. A Google OAuth authorization window will open.
  </Step>

  <Step title="Choose your Google account">
    Select the Google account whose Drive you want to connect. If you need to connect multiple Drive accounts, you can add additional connections after completing the first.
  </Step>

  <Step title="Grant permissions">
    Review the requested Drive permissions and click **Allow**. Atmet requests the scopes required to monitor file changes and perform the file management actions listed below.
  </Step>

  <Step title="Confirm the connection">
    You'll be redirected back to Atmet. A green **Connected** badge confirms your Drive is live and ready to use.
  </Step>
</Steps>

<Note>
  Connecting Google Drive does not grant Atmet access to your entire Drive automatically. Actions only execute on the files and folders you explicitly reference in your workflow steps.
</Note>

***

## Triggers

<Accordion title="File changed">
  Fires when an existing file in your Drive is modified — including edits to Google Docs/Sheets/Slides, file renames, moves, or property updates.

  | Parameter         | Description                                                                                                                            |
  | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
  | `File / Folder`   | Optionally specify a file ID or folder ID to scope the trigger. If left blank, any change in the connected Drive can fire the trigger. |
  | `Include removed` | Whether to also fire when a file is moved to the trash or deleted.                                                                     |

  **Use this trigger when** you want to react to document edits — for example, kicking off a review workflow whenever a shared proposal is updated.
</Accordion>

<Accordion title="New file created">
  Fires whenever a new file or folder is created in your Drive or in a specific folder you specify.

  | Parameter       | Description                                                                                       |
  | --------------- | ------------------------------------------------------------------------------------------------- |
  | `Parent folder` | Optionally restrict the trigger to files created inside a particular folder.                      |
  | `MIME type`     | Optionally filter by file type (e.g., `application/pdf`, `image/png`, or Google Workspace types). |

  **Use this trigger when** you want to start an intake process for new uploads — for example, processing incoming invoice PDFs or triggering a review when a new design file is added to a shared folder.
</Accordion>

***

## Actions

<Accordion title="Reading and searching files">
  | Action         | What it does                                                                                                                            |
  | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
  | **List files** | Returns files and folders matching optional filters (name, MIME type, parent folder, owner). Supports pagination for large directories. |
  | **Get file**   | Retrieves metadata and content for a specific file by its Drive file ID.                                                                |
</Accordion>

<Accordion title="Creating and uploading">
  | Action            | What it does                                                                                                                       |
  | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
  | **Upload file**   | Uploads a new file to Drive. Supports multipart upload for files up to 5 GB. You can specify the destination folder and file name. |
  | **Create folder** | Creates a new folder at a specified path or inside a parent folder.                                                                |
</Accordion>

<Accordion title="Organizing files">
  | Action          | What it does                                                                                  |
  | --------------- | --------------------------------------------------------------------------------------------- |
  | **Copy file**   | Creates a duplicate of an existing file, optionally in a different folder or with a new name. |
  | **Move file**   | Moves a file from one folder to another within Drive.                                         |
  | **Delete file** | Permanently deletes a file or moves it to the trash (configurable).                           |
</Accordion>

<Accordion title="Sharing and permissions">
  | Action         | What it does                                                                                  |
  | -------------- | --------------------------------------------------------------------------------------------- |
  | **Share file** | Grants view, comment, or edit access to a file for a specific user or group by email address. |
</Accordion>

***

## Workflow ideas

<CardGroup cols={2}>
  <Card title="Automatic report distribution" icon="chart-bar">
    Trigger on a new file in a `Reports` folder. Rename it with a timestamp, share it with a distribution list, and post a link in a Slack channel — all without manual steps.
  </Card>

  <Card title="Document approval pipeline" icon="file-circle-check">
    Trigger on file changes in a `Drafts` folder. When a document is updated, send an email or Slack message to the approver with a link, and move it to an `Under Review` folder automatically.
  </Card>

  <Card title="Intake folder processing" icon="folder-open">
    Trigger on new file creation in an intake folder. Extract text with an AI step, categorize the file type, route it to the correct subfolder, and create a tracking row in a Google Sheet.
  </Card>

  <Card title="Backup to Drive on trigger" icon="cloud-arrow-up">
    Trigger on a GitHub push or Notion page update. Generate a file snapshot and upload it to a dedicated Drive backup folder, maintaining a versioned archive of important content.
  </Card>
</CardGroup>

***

## Limitations and notes

<Warning>
  The Google Drive API has daily request quotas. Workflows that run very frequently against large directories (thousands of files) may hit these limits. Use specific folder and file ID filters wherever possible to reduce API call volume.
</Warning>

<Tip>
  When using the **New file created** trigger, set a `Parent folder` ID to avoid triggering on every new file in your entire Drive. Scoping to a specific intake folder keeps your workflow precise and reduces unnecessary executions.
</Tip>

<Info>
  Google Drive's shared drives (formerly Team Drives) are supported. Make sure the connected Google account has the appropriate access level (Contributor or higher) to the shared drive you want to automate.
</Info>

<Accordion title="How do I find a file or folder ID?">
  Open the file or folder in Google Drive in your browser. The URL contains the ID — for files it looks like `https://drive.google.com/file/d/FILE_ID/view`, and for folders like `https://drive.google.com/drive/folders/FOLDER_ID`. Copy the segment between the slashes and use it in your workflow.
</Accordion>