Google Drive Trigger Nexviahub
AI-generatedSummary
Poll Google Drive for file or folder changes and emit matching Drive file metadata as workflow items. Choose a polling schedule, authentication method, target file or folder, and event; folder watches only cover direct children, not subfolders.
Inputs
- Poll Times (required) — Set when polling runs, using a built-in interval or custom cron expression.
- Authentication (required) — Choose OAuth2 or Service Account authentication. OAuth2 uses the required Client ID, Client Secret, and Refresh Token; the Access Token field is declared but not read by the request code.
- Trigger On (required) — Watch changes to a specific file or changes involving a specific folder.
- File (required) — For a specific-file watch, select a Drive file or provide its link or ID.
- Watch For (required) — For a specific file, the only event is File Updated. For a folder, choose file created/updated, folder created/updated, or the watched folder itself updated.
- Folder (required) — For a specific-folder watch, select a folder or provide its link or ID. Changes in subfolders do not trigger this node.
- Options: File Type — For file-created or file-updated events outside a specific-file watch, optionally filter by Google Drive MIME type; defaults to all file types.
Output shape
A list of workflow items, each containing a matching Google Drive file object in its JSON data.
Scheduled polls query for items created or modified since the previous check and emit no items when there are no matches. Manual execution queries one item and raises an error if none match. The specific-file watch filters for the selected file; folder event watches cover direct children, except “Watch Folder Updated,” which matches the watched folder itself.