← Google Drive

New or Modified Folders from Google Drive API

Pipedream makes it easy to connect APIs for Google Drive and + other apps remarkably fast.

Trigger workflow on
New or Modified Folders from the Google Drive API
Next, do this
Connect to 600+ APIs using code and no-code building blocks
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

Trigger a workflow on New or Modified Folders with Google Drive API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Configure the New or Modified Folders trigger
    1. Connect your Google Drive account
    2. Select a Drive
    3. Optional- Configure Watch for changes to file properties
    4. Configure Push notification renewal schedule
  2. Add steps to connect to + APIs using code and no-code building blocks
  3. Deploy the workflow
  4. Send a test event to validate your setup
  5. Turn on the trigger


This is a pre-built, open source component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

New or Modified Folders on Google Drive
Description:Emits a new event any time any folder in your linked Google Drive is added, modified, or deleted


// This source processes changes to any files in a user's Google Drive,
// implementing strategy enumerated in the Push Notifications API docs:
// https://developers.google.com/drive/api/v3/push and here:
// https://developers.google.com/drive/api/v3/manage-changes
// This source has two interfaces:
// 1) The HTTP requests tied to changes in the user's Google Drive
// 2) A timer that runs on regular intervals, renewing the notification channel as needed

import common from "../common-webhook.mjs";
import {
} from "../../constants.mjs";

export default {
  key: "google_drive-new-or-modified-folders",
  name: "New or Modified Folders",
    "Emits a new event any time any folder in your linked Google Drive is added, modified, or deleted",
  version: "0.0.5",
  type: "source",
  // Dedupe events based on the "x-goog-message-number" header for the target channel:
  // https://developers.google.com/drive/api/v3/push#making-watch-requests
  dedupe: "unique",
  methods: {
    _getLastModifiedTimeForFile(fileId) {
      return this.db.get(fileId);
    _setModifiedTimeForFile(fileId, modifiedTime) {
      this.db.set(fileId, modifiedTime);
    getUpdateTypes() {
      return [
    generateMeta(data, ts) {
      const {
        id: fileId,
        name: summary,
      } = data;
      return {
        id: `${fileId}-${ts}`,
    async processChanges(changedFiles, headers) {
      const files = changedFiles.filter(
        // API docs that define Google Drive folders:
        // https://developers.google.com/drive/api/v3/folder
        (file) => file.mimeType === "application/vnd.google-apps.folder",

      for (const file of files) {
        // The changelog is updated each time a folder is opened. Check the
        // folder's `modifiedTime` to see if the folder has been modified.
        const fileInfo = await this.googleDrive.getFile(file.id);

        const lastModifiedTimeForFile = this._getLastModifiedTimeForFile(file.id);
        const modifiedTime = Date.parse(fileInfo.modifiedTime);
        if (lastModifiedTimeForFile == modifiedTime) continue;

        const eventToEmit = {
          change: {
            state: headers["x-goog-resource-state"],
            resourceURI: headers["x-goog-resource-uri"],
            changed: headers["x-goog-changed"], // "Additional details about the changes. Possible values: content, parents, children, permissions"
        const meta = this.generateMeta(file, modifiedTime);
        this.$emit(eventToEmit, meta);

        this._setModifiedTimeForFile(file.id, modifiedTime);


This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.
Google DrivegoogleDriveappThis component uses the Google Drive app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis component uses $.interface.http to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the run() method of the component.
DrivedrivestringSelect a value from the drop down menu.
Watch for changes to file propertieswatchForPropertiesChangesboolean

Watch for changes to file properties
in addition to changes to content. Defaults to false, watching for only changes to content.

Push notification renewal scheduletimer$.interface.timer

The Google Drive API requires occasional renewal of push notification subscriptions. This runs in the background, so you should not need to modify this schedule.


Google Drive uses OAuth authentication. When you connect your Google Drive account, Pipedream will open a popup window where you can sign into Google Drive and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Google Drive API.

Pipedream requests the following authorization scopes when you connect your account:


About Google Drive

Internet-related services and products

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.