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

# Google Drive Hybrid Runner

> Connect Google Drive to Collate using the Hybrid Runner. Deploy the ingestion agent in your environment for secure, private network metadata extraction.

export const ConnectorDetailsHeader = ({name, icon, stage, availableFeatures, unavailableFeatures = [], availableFeaturesCollate = []}) => {
  const showSubHeading = availableFeatures?.length > 0 || unavailableFeatures?.length > 0 || availableFeaturesCollate?.length > 0;
  const totalAvailableFeatures = [...availableFeatures || [], ...availableFeaturesCollate || []];
  return <div className="container">
      <div className="Heading">
        <div className="flex items-center gap-3">
          {icon && <div className="IconContainer">
              <img src={icon} alt={name} noZoom className="ConnectorIcon" />
            </div>}
          <h1 className="ConnectorName">{name}</h1>
          <span className={`StageBadge ${stage === 'PROD' ? 'prod' : 'beta'}`}>
            {stage}
          </span>
        </div>
      </div>
      {showSubHeading && <div className="SubHeading">
          <div className="FeaturesHeading">Feature List</div>
          <div className="FeaturesList">
            {totalAvailableFeatures.map(feature => <div className="FeatureTag AvailableFeature" key={feature}>
                ✓ {feature}
              </div>)}
            {unavailableFeatures.map(feature => <div className="FeatureTag UnavailableFeature" key={feature}>
                ✕ {feature}
              </div>)}
          </div>
        </div>}
    </div>;
};

<ConnectorDetailsHeader icon="/public/images/connectors/googledrive.webp" name="Google Drive" stage="BETA" availableFeatures={["Metadata", "Owners", "Sample Data"]} unavailableFeatures={[]} />

This section provides guides and references to use the Google Drive connector.

Configure and schedule Google Drive metadata and profiler workflows from the Collate UI:

* [Requirements](#requirements)
* [Metadata Ingestion](#metadata-ingestion)
* [Data Profiler](/ai-2-0/how-to-guides/data-quality-observability/profiler/profiler-workflow)

## Requirements

### GCP Credentials

To connect to Google Drive, you'll need to set up a Google Cloud Platform (GCP) service account with the necessary permissions.

#### 1. Create a Service Account

1. Go to the [Google Cloud Console](https://console.cloud.google.com/).
2. Navigate to **IAM & Admin** > **Service Accounts**.
3. Click **Create Service Account**.
4. Provide a name and description for the service account.
5. Grant the service account the necessary roles (at minimum: **Viewer** role).
6. Click **Done**.

#### 2. Enable Google Drive API

1. In the Google Cloud Console, navigate to **APIs & Services** > **Library**.
2. Search for "Google Drive API".
3. Click on it and enable the API.

#### 3. Create and Download Service Account Key

1. Navigate back to **IAM & Admin** > **Service Accounts**.
2. Click on your newly created service account.
3. Go to the **Keys** tab.
4. Click **Add Key** > **Create new key**.
5. Choose **JSON** as the key type.
6. Download the JSON key file.

#### 4. Domain-Wide Delegation (Optional)

If you need to access files owned by other users in your organization:

1. In the service account details, click **Show Domain-Wide Delegation**.
2. Enable **Enable Google Workspace Domain-wide Delegation**.
3. Note the **Client ID**.
4. In Google Workspace Admin Console:
   * Navigate to **Security** > **API Controls** > **Domain-wide Delegation**.
   * Add the Client ID with the following OAuth scopes:
     * `https://www.googleapis.com/auth/drive.readonly`
     * `https://www.googleapis.com/auth/spreadsheets.readonly`
5. Specify the delegated email address in the connection configuration.

### Permissions Required

The service account needs:

* Read access to the Google Drive files and folders you want to ingest
* If using shared drives: Access to the specific shared drive
* If using domain-wide delegation: Domain-wide delegation enabled with appropriate scopes

## Metadata Ingestion

To ingest metadata from Google Drive, you need to create a service connection. The service connects Google Drive with Collate. Once you create a service, Collate automatically starts ingesting metadata.

### Step 1: Add New Service

1. In the left navigation, click **Connections**.
2. On the **Connections** page, click **Add New Service**.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/add-new-service.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=733cef1141ef13d318634aa9f407eb2b" alt="Add New Service" width="2992" height="1256" data-path="public/images/ai-2.0/connectors/metadata-ingestion/add-new-service.png" />

### Step 2: Select a Service and Connector

From the service type dropdown, select **Drive Services**, then click the **Google Drive** connector tile.

<img src="https://mintcdn.com/collatedocs/tVR0kaoXvgs3p2Wx/public/images/ai-2.0/connectors/metadata-ingestion/Drive/select-service/googledrive.png?fit=max&auto=format&n=tVR0kaoXvgs3p2Wx&q=85&s=3fb708c94ddf4063b44b7835faccd208" alt="Select Service" width="2372" height="878" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/select-service/googledrive.png" />

### Step 3: Add Service Name and Description

* Enter a unique, descriptive **Service Name**. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other Google Drive services you are ingesting metadata from.
* Optional: Enter a **Description** for the service.

<img src="https://mintcdn.com/collatedocs/tVR0kaoXvgs3p2Wx/public/images/ai-2.0/connectors/metadata-ingestion/Drive/service-name/googledrive.png?fit=max&auto=format&n=tVR0kaoXvgs3p2Wx&q=85&s=bf1613b2ea196a1aabb4b429d3dd559b" alt="Add New Service Name" width="1458" height="814" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/service-name/googledrive.png" />

<Note>
  **Note**: The service name cannot be changed after it is set.
</Note>

### Step 4: Configure Connection Options

Specify where ingestion runs, provide your source credentials, and verify the connection.

#### Select Ingestion Runner

Select an **Ingestion Runner**: the runner where the ingestion pipeline will execute.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/select-ingestion-runner.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=1249f828648614445e8a976ea1933487" alt="Add Name and Select Ingestion Runner" width="1444" height="506" data-path="public/images/ai-2.0/connectors/metadata-ingestion/select-ingestion-runner.png" />

#### Enter Connection Details

Enter the connection details for Google Drive. The right-hand panel in the UI displays inline help for each field.

<img src="https://mintcdn.com/collatedocs/bWmb7UY94lEjxxg4/public/images/ai-2.0/connectors/metadata-ingestion/Drive/connection-details/googledrive.png?fit=max&auto=format&n=bWmb7UY94lEjxxg4&q=85&s=700362a6d3965074a901881c7fad9f92" alt="Configure Service Connection" width="1442" height="1496" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/connection-details/googledrive.png" />

* **GCP Credentials**: Provide the GCP credentials to access Google Drive API. You can provide the credentials in one of the following ways:
  * **GCP Credentials Path**: Path to the GCP service account credentials JSON file
  * **GCP Credentials Values**: Paste the content of the GCP service account credentials JSON file directly

* **Delegated Email (Optional)**: Email address to impersonate using domain-wide delegation. This is required if you want to access files owned by other users in your organization using domain-wide delegation.

* **Drive ID (Optional)**: Specific shared drive ID to connect to. If provided, only this shared drive will be processed. Leave empty to process all accessible drives.

* **Include Team Drives**: Enable to include shared/team drives in metadata extraction. Default is `true`.

* **Include Google Sheets**: Enable to extract metadata only for Google Sheets files. When enabled, only Google Sheets will be processed. Default is `false`.

* **Directory Filter Pattern (Optional)**: Regex pattern to include or exclude directories from metadata extraction.

* **File Filter Pattern (Optional)**: Regex pattern to include or exclude files from metadata extraction.

* **Spreadsheet Filter Pattern (Optional)**: Regex pattern to include or exclude spreadsheets from metadata extraction (only applies when Include Google Sheets is enabled).

* **Worksheet Filter Pattern (Optional)**: Regex pattern to include or exclude worksheets within spreadsheets from metadata extraction (only applies when Include Google Sheets is enabled).

#### Advanced Configuration

Drive Services have an Advanced Configuration section, where you can pass extra arguments to the connector and, if needed, change the connection Scheme. This would only be required to handle advanced connectivity scenarios or customizations.

* **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to the source during the connection. These details must be added as Key-Value pairs.
* **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent during the connection. These details must be added as Key-Value pairs.

<Tip>
  **Tip**: When using a **Hybrid Ingestion Runner**, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format:

  ```
  password: secret:/my/database/password
  ```

  This applies **only to fields marked as secrets** in the connection form (these typically mask input and show a visibility toggle icon).
  For more information about managing secrets in hybrid setups, see the [Hybrid Ingestion Runner Secret Management Guide](/ai-2-0/getting-started/lets-get-started/ingest-your-data/hybrid-ingestion-runner#manage-secrets)
</Tip>

#### Test Connection

Once the credentials have been added, click on **Test Connection** and **Save** the changes.

<img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/test-connection.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=3365cff7bb9d82c85a2ff9ab559d6f11" alt="Test Connection" width="1446" height="188" data-path="public/images/ai-2.0/connectors/metadata-ingestion/test-connection.png" />

### Step 5: Configure Ingestion Options

In the **What to Ingest** step, use filter patterns to control which assets Collate ingests from your drive service. Filter patterns use regular expressions applied to asset names.

#### How Filter Patterns Work

* **Include**: Add one or more comma-separated regular expressions. Collate ingests only assets whose names match at least one expression. Leave blank to include all assets.
* **Exclude**: Add one or more comma-separated regular expressions. Collate skips any asset whose name matches an expression. Leave blank to exclude nothing.

Rules match asset names using one of five expressions:

* **contains**: matches any name containing the value. For example, `sales` matches `my_sales_data` and `sales_2024`.
* **starts with**: matches names beginning with the value. For example, `prod_` matches `prod_db` and `prod_schema`.
* **ends with**: matches names ending with the value. For example, `_raw` matches `events_raw` and `logs_raw`.
* **is exactly**: matches the exact name only. For example, `analytics` matches only `analytics`.
* **matches regex**: matches names using a regular expression. For example, `^prod_.*_v\d+$` matches `prod_events_v1`.

When both Include and Exclude are set, Exclude takes priority.

<Tip>
  **Tip**: Leave all filter patterns empty to ingest all directories, files, spreadsheets, and worksheets available in the source.
</Tip>

**Filter Options**

The Directory, File, Spreadsheet, and Worksheet sections each include the following filter options:

* **Directory**: Controls which directories (folders) Collate ingests from the source.
* **File**: Controls which individual files within the ingested directories are included.
* **Spreadsheet**: Controls which spreadsheet files are included in metadata ingestion.
* **Worksheet**: Controls which individual worksheets (tabs within a spreadsheet) are included.

Each section provides the following controls:

* **Scan Mode**: You can choose between the following scan modes:
  * **Scan all**: Ingests every asset of that type the connector can access. This is the default.
  * **Only specific**: Enables include rules so only assets matching at least one rule are ingested.
* **Exclude system toggle**: Use this toggle to automatically filter out system-reserved names defined by the connector — for example, **Exclude system databases** for the Databases section.
* **Always exclude**: Add permanent exclusion rules (shown in red). Assets matching these rules are never ingested, regardless of include rules.
* **Preview**: Shows a real-time summary of what will be in scope based on your current rules.
* **Include rules** *(available only in **Only specific** mode)*: Click **+ Add** to define a rule. Added rules appear as chips; an asset is included if it matches any rule.

<Tip>
  **Tip**: If [AutoPilot](/ai-2-0/admin-guide/applications/autopilot) is enabled, usage tracking, data lineage, and other downstream workflows start automatically after the first metadata ingestion completes.
</Tip>

### Step 6: Create & Deploy

Click **Create & Deploy** to deploy the agent and start the first metadata ingestion run. Collate saves the service configuration and immediately begins pulling metadata from the source.

To monitor ingestion progress or view the service you just added, go to **Connections** in the left navigation and select your service.

## Configure Metadata Agent and Schedule Ingestion

The **Metadata Agent** extracts directories, files, spreadsheets, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets.

When you click **Create & Deploy**, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the **Agents** tab on the service detail page.

To configure the additional Metadata Agent and schedule ingestion, follow these steps:

1. In the left navigation, click **Connections** and select your service.

2. Click the **Agents** tab.

3. Click **Add Agent** and select **Metadata** from the dropdown.
   <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/add-metadata-agent.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=accad7d1c4ddf209781bff851d51d464" alt="Add Metadata Agent" width="2398" height="1144" data-path="public/images/ai-2.0/connectors/metadata-ingestion/add-metadata-agent.png" />
   For some services, the dropdown is not available and clicking **Add Agent** takes you directly to the agent configuration page.

4. On the **Configure Ingestion** page, do the following and click **Next**.

   * **Name this Ingestion**: Enter a unique recognizable name for this ingestion pipeline.

     <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/metadata-agent-name.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=d5ec1f0f3742cadab8cd54c602c97239" alt="Name this Ingestion" width="1578" height="644" data-path="public/images/ai-2.0/connectors/metadata-ingestion/metadata-agent-name.png" />

   * **Agent Setup**: Configure the core parameters for this agent. The following fields are available:

     | Field                     | Default | Description                                                                                                                                                       |
     | ------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | Number of Threads         | 1       | Number of threads to use for parallel drive ingestion.                                                                                                            |
     | Mark Deleted Directories  | On      | Soft-delete directories in Collate when they are removed from the source. Associated entities like files, spreadsheets, worksheets, and lineage are also deleted. |
     | Mark Deleted Files        | On      | Soft-delete files in Collate when they are removed from the source. Associated entities like lineage are also deleted.                                            |
     | Mark Deleted Spreadsheets | On      | Soft-delete spreadsheets in Collate when they are removed from the source. Associated entities like worksheets and lineage are also deleted.                      |
     | Mark Deleted Worksheets   | On      | Soft-delete worksheets in Collate when they are removed from the source. Associated entities like lineage are also deleted.                                       |
     | Include Directories       | On      | Fetch directory metadata. Turn off to skip directories entirely.                                                                                                  |
     | Include Files             | On      | Fetch file metadata. Turn off to skip files entirely.                                                                                                             |
     | Include Spreadsheets      | On      | Fetch spreadsheet metadata. Turn off to skip spreadsheets entirely.                                                                                               |
     | Include Worksheets        | On      | Fetch worksheet metadata. Turn off to skip worksheets entirely.                                                                                                   |

     <img src="https://mintcdn.com/collatedocs/tVR0kaoXvgs3p2Wx/public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-agent-setup.png?fit=max&auto=format&n=tVR0kaoXvgs3p2Wx&q=85&s=8a132a356d8ea3314299b648265a253c" alt="Agent Setup" width="1530" height="1558" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-agent-setup.png" />

   * **Filter Patterns**: Apply include or exclude rules to scope which directories, files, spreadsheets, and worksheets this agent ingests. Use FQN for filtering to apply regex on fully qualified names (e.g. `service_name.directory_name.file_name`) instead of raw names. These follow the same filter options described in **Step 5**.

     <img src="https://mintcdn.com/collatedocs/tVR0kaoXvgs3p2Wx/public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-filter-pattern.png?fit=max&auto=format&n=tVR0kaoXvgs3p2Wx&q=85&s=1337b9f82862926e08662b4f1fb0013b" alt="Filter Patterns" width="1570" height="1040" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-filter-pattern.png" />

   * **Scope & Behaviour**: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs:

     | Toggle            | Default | Description                                                                                                                                                            |
     | ----------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     | Enable Debug Log  | Off     | Sets the ingestion log level to DEBUG. Useful for troubleshooting.                                                                                                     |
     | Include Tags      | On      | Ingest tags from the source.                                                                                                                                           |
     | Include Owners    | Off     | Assign owners from the source when the owner email matches a Collate user. Does not overwrite an existing owner.                                                       |
     | Override Metadata | Off     | When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. When off, Collate only updates fields that have no existing value. |

     <img src="https://mintcdn.com/collatedocs/tVR0kaoXvgs3p2Wx/public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-scope-behaviour.png?fit=max&auto=format&n=tVR0kaoXvgs3p2Wx&q=85&s=508c5978a32083dabbc5443f2a1ec4b4" alt="Scope & Behaviour" width="1562" height="894" data-path="public/images/ai-2.0/connectors/metadata-ingestion/Drive/drive-scope-behaviour.png" />

5. On the **Schedule Interval** page, set when the agent runs:

   * **Schedule**: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
   * **On-Demand**: No automatic schedule; trigger the agent manually when needed.

   <img src="https://mintcdn.com/collatedocs/bv5oe4uRjuorTJO1/public/images/ai-2.0/connectors/metadata-ingestion/schedule.png?fit=max&auto=format&n=bv5oe4uRjuorTJO1&q=85&s=25cc1d78f6f2a8bd115830d034d1d8d1" alt="Schedule Interval" width="1588" height="1044" data-path="public/images/ai-2.0/connectors/metadata-ingestion/schedule.png" />

6. Click **Add** to deploy the agent.

## Troubleshooting

<Columns cols={2}>
  <Card title="Google Drive Troubleshooting" href="/ai-2-0/connectors/drive/googledrive/troubleshooting">
    Learn more about how to troubleshoot common Google Drive connector issues and resolve configuration or ingestion errors.
  </Card>
</Columns>
