Skip to main content

Scheduled monitoring of new & modified files across Google Drive folders

Workflow preview

Workflow preview
100%
Scheduled monitoring of new & modified files across Google Drive folders preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This n8n template allows you to, on a schedule, list all files that have been modified since the last execution in a Google Drive folder and in all its subfolders While Google Drive is accessible a...

Best for

  • File Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.splitinbatches, n8n-nodes-base.googledrive, n8n-nodes-base.if, n8n-nodes-base.executeworkflow, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ossian Madisson.

Original n8n.io source

1.1 Workflow description

Title
Scheduled monitoring of new & modified files across Google Drive folders
Workflow name
Scheduled monitoring of new & modified files across Google Drive folders

This n8n template allows you to, on a schedule, list all files that have been modified since the last execution in a Google Drive folder and in all its subfolders

While Google Drive is accessible and easy to use, file listings via API are limited to either all files in the entire Drive or all files in a specific folder. This also means that the n8n triggers for Google Drive are limited to changes to a specific file or folder.

This template is built to replace the built-in trigger nodes in the situations when you need to trigger on new or changed files in a folder or any of its subfolders.

Use cases

  • Trigger a RAG pipeline to update with new or updated documents
  • Push newly uploaded or updated documents into CMS, project management tool or other external platform
  • Log changes to build an audit trail
  • Trigger a backup job or sync process only for files that have changed since the last run, saving bandwidth and processing time.
  • Notify team or client about new documents
  • Can also be run without the scheduling part to perform a one-time iteration of all files

Good to know

  • Works well if you attach a loop node to the "output node" to run additional actions on the files
  • The workflow is designed to use a minimal amount of custom code, preferring built-in nodes in n8n
  • Does not identify file removals

How it works

  • Recursively executes a subworkflow for each folder in the main folder
  • Each subworkflow execution sends a list of all files in the folder to an "output node" that checks if the files was created or modified since the last execution
  • When all subworkflows have been executed, the files in the main folder are sent to the "output node"
  • A persistent variable (time of trigger node activation) is set for timestamp comparison on the next execution (this is only set on non-manually triggered active workflow executions)

How to use

  • Set schedule interval in the trigger node (default every 60min)
  • Add Google Drive credentials to the four Google Drive nodes
  • Define your main/root folder in the two nodes inside the red box
  • Connect your workflow to process the files after the node in the yellow box, please note that there will be "one output" per folder

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Loop all subfolders

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 4 - List folders

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 5 - If subfolders exist

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 6 - Trigger recursion to next level

Type / Role
n8n-nodes-base.executeWorkflow - executeWorkflow
Config choices
Version 1.2

Block 7 - List folders in root

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 8 - List all files in root

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 9 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Start recursion

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1.1

Block 11 - Trigger recursion of first level

Type / Role
n8n-nodes-base.executeWorkflow - executeWorkflow
Config choices
Version 1.2

Block 12 - List all files

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 13 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 15 - SetStartTime

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 16 - Outputs new or updated files

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 17 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - If folders exist

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 19 - Exit sub workflow

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 20 - Wait for file comparison to complete

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

3. Summary Table

Workflow Scheduled monitoring of new & modified files across Google Drive folders
Complexity advanced
Nodes 20
Categories File Management
Author Ossian Madisson
Published 02 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/9209/9209.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Scheduled monitoring of new & modified files across Google Drive folders do?

This n8n template allows you to, on a schedule, list all files that have been modified since the last execution in a Google Drive folder and in all its subfolders While Google Drive is accessible a...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.