Skip to main content
provider: "gdrive" · Import and export · Requires enablement The Google Drive connector links a folder in My Drive or a shared drive to a vault, in either direction.
Google Drive requires enablement for your organization before it will authorize. Until then, POST /connectors/v1/connections returns 403 connector_scope_not_enabled. Contact support to request access.Check the providers array from GET /connectors/v1/connections before showing a Drive option in your UI.

Browsing

Browse with no parameters to list My Drive and any shared drives the connected user can reach, then descend by folder.
cURL
Response
Drive folder ids are globally unique, so a link’s identity rests on folder_id alone. container_id is present only for shared drives; absent or root means My Drive.

Importing a folder

cURL
Everything under the selected folder is imported recursively.

Change detection

Drive has a native change feed, so incremental runs are cheap. On a backfill, the connector captures a change token before it walks the folder, so edits made during a long walk land in the next run rather than falling into a gap. Large folders checkpoint as they go and resume without restarting from the root. If a stored change token ages out, Drive reports 410 and the connector re-backfills automatically. The ledger deduplicates unchanged files by content version, so a re-backfill does not re-import anything.

Content identity

Version identity is the cheapest signal that changes only when content changes—a checksum for ordinary files, and version plus modification time for Google-native documents. A rename or a move therefore updates metadata without re-downloading the file.

Export

Drive supports direction: "export" and direction: "both". With both, exports default to a CaseMark Output subfolder under the import root, and that subfolder is excluded from the import side so exported files are never re-imported. Export never deletes anything in Drive.

Rate budget

Drive allows 12,000 requests per minute with four concurrent transfers. In practice you are far more likely to be bounded by vault ingestion throughput than by Drive. A large folder does not start every ingestion at once: imports commit through a bounded preparation window and then queue into the shared ingestion dispatcher.

Reconnection

Google refresh tokens are long-lived, so reconnection is rare once a user has consented.

Capabilities at a glance

Next steps

Import & Export

Link mechanics, policies, and progress

Errors & Recovery

Reauthorization, access loss, and throttling

All providers

Compare against the other supported providers