Google Drive Trigger

Node catalog Triggers

On this page

Start the workflow when a file is added or updated in Google Drive.

Usage and specifics

Choose a Google Drive credential, parent folder, event and interval. Publish to initialize the baseline; subsequent changes are detected by polling.

Technical type : google_drive_trigger. Runtime : nodulz.

Credentials and prerequisites

Google Drive (integration / google_drive). Google service account JSON key with access to files and shared drives.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`parentId`	`string`	`""`	-
`event`	`enum`	`"file_added"`	`file_added`, `file_updated`, `file_added_or_updated`
`pollInterval`	`number`	`60`	-; ≥ 30, ≤ 86400

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "parentId": "",
  "event": "file_added",
  "pollInterval": 60
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.