Google Drive integration

What it does

The Google Drive integration lets your agency move files in and out of a client's Drive and start workflows whenever new files land. Connect a client's Google account once and your workflows can upload an attachment from a form submission, search Drive for files matching a query, copy a template into a client folder, download a file's bytes into a downstream step, delete stale files on a schedule, or kick off a workflow the moment a new file appears in a watched folder.

Connect a Google Drive account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Google Drive and click Connect.
3. Sign in with the Google account whose Drive files you want to manage on behalf of your client.
4. Grant the requested scopes (full read and write access to Drive so TaskJuice can upload, copy, download, and delete files).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit Google Account permissions and remove the TaskJuice entry.

Triggers

• google-drive/new-file polls Drive on a configurable interval and emits one activation per cycle containing every file observed since the last cycle. Filter by an optional Drive search query, a folder ID, or include trashed files. Drop a Loop node downstream to process each file individually, or feed the array straight into a digest.

Actions

• google-drive/create-drive-file creates a new file with metadata only (name, MIME type, optional parent folders), useful for placeholder records or for materializing a Google Doc or Sheet to be filled in later.
• google-drive/upload-file uploads a file's bytes (from a previous step's FileReference or a file-upload field) with metadata in a single multipart request.
• google-drive/list-files searches Drive with the standard q query syntax, with paging, field selection, and order controls.
• google-drive/get-file retrieves the metadata for a single file by its Drive ID.
• google-drive/download-file downloads the file's bytes and returns a FileReference that downstream steps can attach to outbound emails, forward to other apps, or persist.
• google-drive/copy-file creates a copy of an existing file, optionally renaming it and placing it in a different folder.
• google-drive/delete-file permanently deletes a file by its Drive ID.

Known limitations

• The new-file trigger is polling-based. Google Drive's push-notification surface requires a registered webhook callback per watched resource and expires every few days, so TaskJuice runs a polling cycle (60 seconds minimum, five minutes by default) and emits files observed since the last watermark. Latency is bounded by the chosen interval rather than instant.
• The Drive API enforces per-user and per-project quotas. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• Selectable files in the resource picker are loaded with the configured fields projection (files(id,name,mimeType)). Files the connected user cannot see in Drive will not appear in the picker.
• Google Workspace native files (Docs, Sheets, Slides) cannot be downloaded with download-file directly. Use the standard Drive export workflow upstream or fetch them through the relevant Workspace integration.