Skip to main content
Use the @bijectionhq/connectors/google-drive entrypoint to declare Google Drive resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Google Drive

incremental: Paged metadata and independent content

The following example matches configuration standard.

Configuration: standard

Case: google-drive/drive/incremental/standard. Connection and resource configuration are declared by this exact case. Credential kind: google-drive. Keep credential material in the private credential inventory.
Native admission analysis has not been recorded for this artifact. Declared configuration does not establish native guarantees or provider behavior. Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: pdfExports

Case: google-drive/drive/incremental/pdfExports. Connection and resource configuration are declared by this exact case. Credential kind: google-drive. Keep credential material in the private credential inventory.
Native admission analysis has not been recorded for this artifact. Declared configuration does not establish native guarantees or provider behavior. Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

references: Metadata only

The following example matches configuration standard.

Configuration: standard

Case: google-drive/drive/references/standard. Connection and resource configuration are declared by this exact case. Credential kind: google-drive. Keep credential material in the private credential inventory.
Native admission analysis has not been recorded for this artifact. Declared configuration does not establish native guarantees or provider behavior. Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Bind driveId to a shared drive ID, or the empty string for the authenticated user’s accessible files. The private google-drive OAuth credential needs https://www.googleapis.com/auth/drive.readonly. This mode does not claim that a drive.file grant can enumerate an entire drive. Consent and account selection remain deployment configuration. The reader saves a startPageToken before listing files, publishes bounded pages, then reads changes from that saved token to catch edits made during the listing. It stores nextPageToken and newStartPageToken without ordering or incrementing them. Empty continuation pages still advance. A 410 explicitly restarts bootstrap; other failures retain the previous position. Incomplete searches are refused. None of these pages claims a transactionally consistent multi-page snapshot or a complete historical change log. File IDs remain the record identity across renames and moves. items retains names, parent IDs, MIME type, provider version, content fingerprint, size, shortcut target and download capability. Removal means removal from this source’s visible scope, not proof of permanent deletion. Shortcuts are references; this mode does not follow arbitrary targets. contents copies downloadable blob files using files.get?alt=media. With an explicit exportMimeType, exports separately acquires downloadable Workspace documents through files.export, subject to Google’s 10 MiB export limit. Unsupported export formats remain unresolved. Exports retain their explicit representation; they are not original file bytes. Metadata and byte acquisition have independent schedules and durable responsibilities. Host-computed SHA-256 identifies acquired bytes. Provider MD5 and opaque revisions keep separate names. googleDrive.drive.references() declares only metadata endpoints and needs the narrower drive.metadata.readonly OAuth scope. It exposes no content or export table. The protected file ceiling is 1 GiB (256 MiB by default). A refused or incomplete transfer leaves work pending. Provider capabilities are observed metadata and do not become application ACLs. This is an application-governed, read-only mode; no live Drive qualification is established by declaration export or portable fixtures.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: fbd2178c1f8638d0353b9195aeab0c67b238d5965f8f1d8f9781c921460142d9. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.