Skip to main content
Waaru
Active integration

Connect Google Drive and approve specific files or folders.

The connector uses drive.file access and opaque resource bindings. It does not search the account or accept arbitrary Drive IDs.

Google Drive integration

Move a customer file through a Drive location you selected.

Choose the files and folders Waaru may use through Google Picker. A workflow can read safe metadata, upload private WhatsApp media, import a selected binary file, or create a subfolder without broad account access.

In one line

Waaru works only with Google Drive items the operator selects. It can read safe metadata, move private media in either direction, and create a subfolder below an approved folder.

Capability review updated .

Maintained by the Waaru product team. Read our editorial and product-claim review method.

No credit card. No commitment.

Keep file access as narrow as the workflow.

The operator chooses the location first. Later workflow actions resolve that workspace-owned binding again before moving private media.

ExampleGoogle Drive file handoff

Customer documents

One operator-approved Drive location.

Operating boundary

Review what this connection can do.

Authorization

The operator selects approved files and folders through Google Picker. Waaru uses file-scoped access and opaque bindings.

Reads

Read safe metadata for one selected file or folder, or import one selected binary file into private Waaru media.

Writes

Upload private workspace media to a selected folder or create one subfolder below an approved folder.

Events

Drive change events are not part of this connector.

Setup

Connect Google Drive, select each approved item, and test the exact upload or import used by the workflow.

Exclusions

No account-wide search, sharing, public links, delete, move, rename, overwrite, Google-native export, or raw API calls.

Recovery

Uploads and folder creates use pre-generated IDs and an execution marker so an uncertain result can be reconciled without duplicates.

Selection

Approve the item through Google Picker.

The browser sends a selected Google item to the binding endpoint. Waaru verifies access with the connected account and stores an opaque workspace-owned binding; the workflow never receives or accepts a raw Google file ID.

Available actions

Handle four bounded file operations.

  • Read safe metadata for one selected file or folder
  • Upload private workspace media to a selected folder
  • Import a selected binary Drive file into private Waaru media
  • Create a subfolder below a selected folder

Recovery

Reconcile a file create instead of repeating it blindly.

Uploads and folder creates use Google pre-generated IDs and an execution marker. Writes make one provider attempt, allowing an ambiguous result to be reconciled without creating duplicate files or folders.

Current boundary

The connector does not administer the Drive account.

Account-wide search, broad Drive scopes, sharing, permissions, public links, delete, move, rename, overwrite, Google-native document export, raw API calls, and Drive change events are outside the release.

FAQ

Questions worth answering.

Yes. It can upload private workspace media to a folder the operator selected through Google Picker.

Research notes

Evidence checked for this page.

Primary Google references for Picker, file-scoped authorization, and uploads.

  • Google Picker lets a user select Drive files for an application.

    Google for Developers · Accessed 13 August 2026

  • Google describes drive.file as access to files a user opens or shares with an app.

    Google for Developers · Accessed 13 August 2026

  • Google Drive documents simple, multipart, and resumable file uploads.

    Google for Developers · Accessed 13 August 2026

Keep reading.

Compare

Evaluating platforms? Every claim cited, every price dated.

Ready to ship a WhatsApp flow that doesn't break?

Apply for founding access. No credit card. Cancel anytime.

See pricing