Google Drive Trigger

Trigger a workflow when a watched Google Drive file or folder changes, using Drive's files.watch push notifications.

The trigger authenticates through a Google connection. Connect a Google account once and pick it in the node's settings.

When to Use

Use Google Drive Trigger when:

A file shared with your team is updated and downstream steps should react (reindex, notify, archive)
You want an event-driven alternative to polling a Drive folder

Google Account — required. Pick a Google connection from the Connections page.

Handle	Type	Description
`payload`	object	Normalized Drive change event

The payload (accessed as {{ google_drive.* }}) shape:

Field	Type	Description
`type`	string	Event type (e.g. `update`, `change`)
`file_id`	string	ID of the file or folder that changed
`resource_state`	string	Drive resource state reported by the notification

Setting	Type	Default	Description
`file_id`	string	—	Required. Google Drive file or folder ID to watch. Supports `{{ }}` bindings.

Setting	Type	Default	Description
`event_types`	multi-select	`update`, `change`	Resource states that start a run.

Setting	Type	Default	Description
`mockPayload`	code editor (JSON)	sample change event	JSON payload injected for local test runs instead of a real Drive notification.

Post to Slack whenever a shared spec document changes:

Google Drive Trigger → Slack Send Message

Google Drive Trigger settings:

Slack Send Message settings:

Channel: #spec-updates
Text: Spec doc {{ google_drive.file_id }} was updated ({{ google_drive.resource_state }}).