Integration reference

Google Drive Trigger and Action reference

React to files, folders, comments, spreadsheets, presentations, shared drives, and access proposals, then manage Drive content.

Authentication

Connect a Google account through OAuth with access to the selected My Drive or shared-drive resources.

• Trigger account type: oauth2; reconnect by oauth.
• Action connection type: oauth2; available modes: Connected Google Drive account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: openid, email, profile, https://www.googleapis.com/auth/drive.readonly.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Google Drive as a Trigger

The current provider manifest contains 18 available Trigger definitions. Representative definitions include:

• New Files (Instant)
• New Files (Polling)
• New or Modified Files
• Changes to Specific Files
• New Shared Drive
• New Access Proposal

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Google Drive Actions

The current Action manifest contains 81 operations. Representative Actions include:

• Upload File
• Find or Create Folder
• Create Text File
• Create Folder
• Copy File
• Move File
• Share File
• Move File to Trash

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

1. Create a Source using a Google Drive Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required Google Drive Action and select the connected account.
4. Map Trigger or earlier-Step data into the Action fields with the field picker.
5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Google Drive.

Troubleshooting Google Drive

The account is missing or cannot be selected

Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.

A resource picker is empty

Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.

The editor asks for additional scopes

Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.

An active Workflow returns 401, 403, or a permission error

Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.

The provider returns 429 or a temporary 5xx

Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

• Choose shared-drive variants when the resource does not live in My Drive.
• Instant notification channels and polling definitions have different latency and lifecycle behavior.

Next

• Explore Google Drive integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations