Reference · built on requestConnectorFiles, documents & spreadsheets

Google Drive

Files, folders, shared drives, permissions, and change notifications from Google Drive through the Drive API v3.

Request accessPricing ↗

About

Google Drive is the file store inside Google Workspace. The Drive API v3 exposes files and folders, shared drives, permissions, revisions, comments and replies, labels, and a changes collection that records what moved. Push notifications on the files and changes resources post an empty HTTPS request to your endpoint when something changes.

Through Fibric, an operator watches a folder or a shared drive, reads the change feed, and proposes an upload, a move, or a permission change. You approve it in Drive's own terms. A receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Google Drive and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Files and folders through files.list and files.get, with the metadata fields the Drive API defines
  • Shared drives, and the files inside them, as collaborative storage owned by multiple users
  • Permissions on a file or folder, including access proposals and approvals
  • Revisions of a file, and the comments and replies attached to it
  • Labels applied to files, with the custom taxonomy and field values your admins define
  • Changes for a user or a shared drive through changes.getStartPageToken and changes.list, paged with nextPageToken
  • Push notifications from files.watch and changes.watch, delivered as empty POST requests with X-Goog-Resource-State headers

Proposed actions

  • Target capability: propose an upload or an update of a file through the files resource, with the target folder named
  • Target capability: propose a move, a rename, or a shortcut to a file or folder
  • Target capability: propose a permission change on a file or folder through the permissions resource
  • Target capability: propose a label on a file, using a label and field your admins already defined

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Keep an evidence folder complete

    The operator watches a shared drive for the documents a policy requires, records each arrival from the changes feed, and proposes a request for what is missing before an audit date.

    With Compliance Evidence, Audit Trail

  • Watch storage growth on shared drives

    The operator reads file sizes and revisions across shared drives, flags folders that grow past the level you set, and proposes an archive move for your approval.

    With Storage Growth

  • Assemble the board pack

    The operator collects the files named in a pack list from Drive, checks each one's last revision, and proposes the pack with a note on anything stale.

    With Board Pack, Meeting Prep

Requirements

  • A Google Cloud project with the Drive API enabled and an OAuth 2.0 client
  • The scopes you need; drive, drive.readonly, and drive.metadata.readonly are restricted scopes that require app verification
  • For push notifications, an HTTPS endpoint with a valid certificate; self-signed certificates are rejected
Authentication
An OAuth 2.0 app authorized by a user or a domain administrator; drive.file covers files the app creates or opens, drive.readonly reads everything, and drive grants full access.

Limits

  • Quota is 1,000,000 units per minute per project and 325,000 per minute per user; files.list costs 100 units, files.get 5, files.download 200
  • Watch channels expire: at most one day on files and one week on changes, so they must be renewed
  • Notifications carry no body; every notification triggers a read of changes.list to learn what changed
  • Restricted scopes such as drive and drive.readonly are granted only to specific app categories after verification

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Google Drive ↗

Questions and answers

Does the Drive API send notifications when a file changes?
Yes. files.watch and changes.watch open a notification channel to an HTTPS endpoint. Each notification is an empty POST with headers such as X-Goog-Channel-ID, X-Goog-Resource-State, and X-Goog-Resource-URI. Channels expire after at most one day for files and one week for changes, so they are renewed.
Which OAuth scopes does Google treat as restricted?
drive, drive.readonly, drive.activity, drive.activity.readonly, drive.metadata, drive.metadata.readonly, drive.meet.readonly, and drive.scripts. Restricted scopes need app verification and are granted only to specific app categories. drive.file, drive.appdata, and drive.install are non-sensitive.
How is Drive API usage metered?
In quota units. The default is 1,000,000 units per minute per project and 325,000 per minute per user per project. files.get costs 5 units, files.list 100, files.download 200, and files.update 50. Exceeding a limit returns 403 or 429, and Google recommends exponential backoff.
Ask about Google Drive

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Google Drive through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy