Analytics preference

We only load Google Analytics after you opt in. You can change this choice at any time from Cookie settings.

Google Drive Trigger

The Google Drive Trigger node watches a Google Drive folder, or one file, and starts a workflow once for each file that is created, updated, or deleted.

The Google Drive Trigger node watches a Google Drive folder, or one file, and starts a workflow once for each file that is created, updated, or deleted. It is a zero-input trigger for intake folders, shared contract folders, and report drops.

Overview

PropertyValue
Inputs0
Outputs1
Output$nodeLabel.event, $nodeLabel.file, $nodeLabel.changed_fields, $nodeLabel.folder_id, $nodeLabel.triggered_at

Parameters

ParameterTypeDescription
credentialIdUUIDgoogle_drive credential
gdtScopefolder | fileWatch the files in a folder (default) or one file
gdtFolderIdStringFolder ID or URL. Empty watches My Drive. Only files directly inside the folder are watched
gdtFileIdStringFile ID or URL, for file scope
gdtEventsArrayAny of created, updated, deleted (default all three). File scope has no created
gdtIncludeFoldersBooleanSubfolders themselves also start runs (default off)
pollIntervalMinutesIntegerHow often Heym checks Drive (minimum and default 1)

These fields take plain values, not $ expressions.

Setup Guide

  1. Create a Google Drive (OAuth2) credential. See Third-Party Integrations.
  2. Drag Google Drive Trigger onto the canvas and select the credential.
  3. Paste the folder URL from your browser, choose the events, and save.

Trigger Semantics

  • The first poll records the folder as it is and starts nothing. Only later changes start runs.
  • created: a file appears in the folder, including a file moved into it.
  • updated: the file's name, modification time, size, or type changed.
  • deleted: the file is no longer in the folder. It was trashed, deleted, or moved out. In file scope, a file you can no longer see counts as deleted.
  • Each change starts exactly one run with trigger_source = "google_drive", also when Heym runs several workers or instances. If a run cannot start, the change is tried again on the next poll. A server crash in the moment between recording a change and starting its run can drop that one change; it is never run twice.
  • At most 50 runs start per poll; the rest follow on the next polls.
  • A folder with more than 5,000 files is skipped with a warning in the logs.
  • Changing the credential, folder, file, or the subfolder setting records the folder again without starting runs. Deactivating the node forgets the folder; changes made while it is inactive do not start runs.

Output Fields

ExpressionDescription
$nodeLabel.eventcreated, updated, or deleted
$nodeLabel.file.idDrive file ID
$nodeLabel.file.nameFile name
$nodeLabel.file.mime_typeFile type
$nodeLabel.file.size_bytesSize, null for Google Docs, Sheets, Slides and folders
$nodeLabel.file.created_timeCreation time
$nodeLabel.file.modified_timeLast modification time
$nodeLabel.file.web_view_linkLink to open the file
$nodeLabel.file.is_foldertrue for subfolders
$nodeLabel.changed_fieldsFields that changed, on updated
$nodeLabel.folder_idWatched folder, root for My Drive, null in file scope
$nodeLabel.triggered_atWhen the change was seen

For deleted, file holds the last metadata Heym saw.

What Heym Stores

Heym keeps the metadata of the watched files (ID, name, type, size, times, link) to tell what changed. It never reads or stores file contents.

Example Workflow

New contract in a folder: summarize and post to Slack

googleDriveTrigger → condition → googleDrive (syncToHeymDrive) → converter (pdfToText) → llm → slack
  • Condition: $contractsFolder.event == "created"
  • Google Drive: gdFileId is $contractsFolder.file.id