Google Drive Connector

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
• Metadata Ingestion
• Data Profiler
• Troubleshooting

​

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

​

Step 2: Select a Service and Connector

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

​

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.

​

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.

​

Enter Connection Details

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

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

​

Test Connection

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

​

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

​

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

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

     
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.
   
6. Click Add to deploy the agent.

​

Troubleshooting