← Google Drive + Front integrations

Import Message with Front API on Changes to Specific Files from Google Drive API

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

Trigger workflow on
Changes to Specific Files from the Google Drive API
Next, do this
Import Message with the Front API
No credit card required
Intro to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜

Trusted by 800,000+ developers from startups to Fortune 500 companies

Adyen logo
Appcues logo
Bandwidth logo
Checkr logo
ChartMogul logo
Dataminr logo
Gopuff logo
Gorgias logo
LinkedIn logo
Logitech logo
Replicated logo
Rudderstack logo
SAS logo
Scale AI logo
Webflow logo
Warner Bros. logo
Adyen logo
Appcues logo
Bandwidth logo
Checkr logo
ChartMogul logo
Dataminr logo
Gopuff logo
Gorgias logo
LinkedIn logo
Logitech logo
Replicated logo
Rudderstack logo
SAS logo
Scale AI logo
Webflow logo
Warner Bros. logo

Developers Pipedream

Getting Started

This integration creates a workflow with a Google Drive trigger and Front action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the Changes to Specific Files trigger
    1. Connect your Google Drive account
    2. Optional- Configure Drive
    3. Optional- Configure Watch for changes to file properties
    4. Configure Push notification renewal schedule
    5. Optional- Select one or more Files
    6. Select one or more Types of updates
  3. Configure the Import Message action
    1. Connect your Front account
    2. Select a Inbox ID
    3. Configure Handle
    4. Optional- Configure Name
    5. Optional- Select a Author ID
    6. Configure To
    7. Optional- Configure CC
    8. Optional- Configure BCC
    9. Optional- Configure Subject
    10. Configure Body
    11. Select a Body Format
    12. Configure External ID
    13. Configure Created At
    14. Optional- Select a Type
    15. Optional- Select a Assignee ID
    16. Optional- Select one or more Tag IDs
    17. Optional- Select a Thread Ref
    18. Configure Is Inbound
    19. Optional- Configure Is Archive
    20. Optional- Configure Should Skip Rules
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are 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.

Trigger

Description:Watches for changes to specific files, emitting an event any time a change is made to one of those files. To watch for changes to [shared drive](https://support.google.com/a/users/answer/9310351) files, use the **Changes to Specific Files (Shared Drive)** source instead.
Version:0.1.3
Key:google_drive-changes-to-specific-files

Google Drive Overview

Using the Google Drive API, you can build applications that:

  • Create and manage files and folders
  • Download and upload files
  • Share and organize files
  • Search for files
  • Track changes to files
  • And much more!

Trigger Code

import cronParser from "cron-parser";
import sampleEmit from "./test-event.mjs";
import includes from "lodash/includes.js";
import { v4 as uuid } from "uuid";

import { MY_DRIVE_VALUE } from "../../constants.mjs";

import changesToSpecificFiles from "../changes-to-specific-files-shared-drive/changes-to-specific-files-shared-drive.mjs";

/**
 * This source uses the Google Drive API's
 * {@link https://developers.google.com/drive/api/v3/reference/files/watch files: watch}
 * endpoint to subscribe to changes to specific files in the user's drive.
 */
export default {
  ...changesToSpecificFiles,
  key: "google_drive-changes-to-specific-files",
  name: "Changes to Specific Files",
  description: "Watches for changes to specific files, emitting an event any time a change is made to one of those files. To watch for changes to [shared drive](https://support.google.com/a/users/answer/9310351) files, use the **Changes to Specific Files (Shared Drive)** source instead.",
  version: "0.1.3",
  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",
  props: {
    ...changesToSpecificFiles.props,
    drive: {
      type: "string",
      label: "Drive",
      description: "Defaults to `My Drive`. To use a [Shared Drive](https://support.google.com/a/users/answer/9310351), use the **Changes to Specific Files (Shared Drive)** source instead.",
      optional: true,
      default: MY_DRIVE_VALUE,
    },
    updateTypes: {
      propDefinition: [
        changesToSpecificFiles.props.googleDrive,
        "updateTypes",
      ],
    },
  },
  hooks: {
    ...changesToSpecificFiles.hooks,
    async activate() {
      // Called when a component is created or updated. Handles all the logic
      // for starting and stopping watch notifications tied to the desired
      // files.

      // You can pass the same channel ID in watch requests for multiple files, so
      // our channel ID is fixed for this component to simplify the state we have to
      // keep track of.
      const channelID = this._getChannelID() || uuid();

      // Subscriptions are keyed on Google's resourceID, "an opaque value that
      // identifies the watched resource". This value is included in request
      // headers, allowing us to look up the watched resource.
      let subscriptions = this._getSubscriptions() || {};

      const files = this.files;
      for (const fileID of files) {
        const {
          expiration,
          resourceId,
        } = await this.googleDrive.activateFileHook(
          channelID,
          this.http.endpoint,
          fileID,
        );
        // The fileID must be kept with the subscription metadata so we can
        // renew the watch request for this specific file when it expires.
        subscriptions[resourceId] = {
          expiration,
          fileID,
        };
      }

      // Save metadata on the subscription so we can stop / renew later
      this._setSubscriptions(subscriptions);
      this._setChannelID(channelID);
    },
    async deactivate() {
      const channelID = this._getChannelID();
      if (!channelID) {
        console.log(
          "Channel not found, cannot stop notifications for non-existent channel",
        );
        return;
      }

      const subscriptions = this._getSubscriptions() || {};
      for (const resourceId of Object.keys(subscriptions)) {
        await this.googleDrive.stopNotifications(channelID, resourceId);
      }

      // Reset DB state
      this._setSubscriptions({});
      this._setChannelID(null);
    },
  },
  methods: {
    ...changesToSpecificFiles.methods,
    _getSubscriptions() {
      return this.db.get("subscriptions") || {};
    },
    _setSubscriptions(subscriptions) {
      this.db.set("subscriptions", subscriptions);
    },
    _getNextTimerEventTimestamp(event) {
      if (event.cron) {
        return cronParser
          .parseExpression(event.cron)
          .next()
          .getTime();
      }
      if (event.interval_seconds) {
        return Date.now() + event.interval_seconds * 1000;
      }
    },
    async renewFileSubscriptions(event) {
      // Assume subscription & channelID may all be undefined at
      // this point Handle their absence appropriately.
      const subscriptions = this._getSubscriptions() || {};
      const channelID = this._getChannelID() || uuid();

      const nextRunTimestamp = this._getNextTimerEventTimestamp(event);

      for (const [
        currentResourceId,
        metadata,
      ] of Object.entries(subscriptions)) {
        const { fileID } = metadata;

        const subscription = {
          ...metadata,
          resourceId: currentResourceId,
        };
        const {
          expiration,
          resourceId,
        } = await this.googleDrive.renewFileSubscription(
          subscription,
          this.http.endpoint,
          channelID,
          fileID,
          nextRunTimestamp,
        );
        subscriptions[resourceId] = {
          expiration,
          fileID,
        };
      }
      this._setSubscriptions(subscriptions);
      this._setChannelID(channelID);
    },
  },
  async run(event) {
    // This function is polymorphic: it can be triggered as a cron job, to make sure we renew
    // watch requests for specific files, or via HTTP request (the change payloads from Google)

    // Component was invoked by timer
    if (event.timestamp) {
      return this.renewFileSubscriptions(event);
    }

    const channelID = this._getChannelID();
    let subscriptions = this._getSubscriptions() || {};

    const { headers } = event;

    if (
      !headers["x-goog-resource-state"] ||
      !headers["x-goog-resource-id"] ||
      !headers["x-goog-resource-uri"] ||
      !headers["x-goog-message-number"]
    ) {
      console.log("Request missing necessary headers: ", headers);
      return;
    }

    const incomingChannelID = headers["x-goog-channel-id"];
    if (incomingChannelID !== channelID) {
      console.log(
        `Channel ID of ${incomingChannelID} not equal to deployed component channel of ${channelID}`,
      );
      return;
    }

    if (subscriptions[headers["x-goog-resource-id"]] === undefined) {
      console.log(
        `Resource ID of ${headers["x-goog-resource-id"]} not currently being tracked. Exiting`,
      );
      return;
    }

    if (!includes(this.updateTypes, headers["x-goog-resource-state"])) {
      console.log(
        `Update type ${headers["x-goog-resource-state"]} not in list of updates to watch: `,
        this.updateTypes,
      );
      return;
    }

    // We observed false positives where a single change to a document would trigger two changes:
    // one to "properties" and another to "content,properties". But changes to properties
    // alone are legitimate, most users just won't want this source to emit in those cases.
    // If x-goog-changed is _only_ set to "properties", only move on if the user set the prop
    if (
      !this.watchForPropertiesChanges &&
      headers["x-goog-changed"] === "properties"
    ) {
      console.log(
        "Change to properties only, which this component is set to ignore. Exiting",
      );
      return;
    }

    const file = await this.googleDrive.getFileMetadata(
      headers["x-goog-resource-uri"],
    );

    if (!file || !Object.keys(file).length) {
      console.log("No file metadata returned, nothing to emit");
      return;
    }

    this.processChange(file, headers);
  },
  sampleEmit,
};

Trigger Configuration

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.
LabelPropTypeDescription
Google DrivegoogleDriveappThis component uses the Google Drive app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between executions.
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.
Drivedrivestring

Defaults to My Drive. To use a Shared Drive, use the Changes to Specific Files (Shared Drive) source instead.

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.

Filesfilesstring[]Select a value from the drop down menu.
Types of updatesupdateTypesstring[]Select a value from the drop down menu:syncaddremoveupdatetrashuntrashchange

Trigger Authentication

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:

emailprofilehttps://www.googleapis.com/auth/drivehttps://www.googleapis.com/auth/drive.readonly

About Google Drive

Google Drive is a file storage and synchronization service which allows you to create and share your work online, and access your documents from anywhere.

Action

Description:Appends a new message into an inbox. [See the docs here](https://dev.frontapp.com/reference/import-inbox-message).
Version:0.1.6
Key:frontapp-import-message

Front Overview

With the Front API, you can build a variety of applications and integrations to
help you and your team manage your email inboxes. Here are a few examples of
what you can build:

  • A personalized email assistant that can help you triage and respond to emails
  • An integration with your CRM that automatically adds emails from customers to
    your CRM
  • A tool that flags important emails and sends you notifications about them
  • An app that helps you find emails from a specific sender or with a certain
    subject line
  • A script that archives all of your old emails

These are just a few examples of what you can build with the Front API – the
possibilities are really only limited by your imagination!

Action Code

import utils from "../../common/utils.mjs";
import frontApp from "../../frontapp.app.mjs";

export default {
  key: "frontapp-import-message",
  name: "Import Message",
  description: "Appends a new message into an inbox. [See the docs here](https://dev.frontapp.com/reference/import-inbox-message).",
  version: "0.1.6",
  type: "action",
  props: {
    frontApp,
    inboxId: {
      propDefinition: [
        frontApp,
        "inboxId",
      ],
    },
    handle: {
      type: "string",
      label: "Handle",
      description: "Handle used to reach the contact. Can be an email address, a twitter, handle, a phone number, custom handle ...",
    },
    name: {
      type: "string",
      label: "Name",
      description: "Name of the contact.",
      optional: true,
    },
    authorId: {
      propDefinition: [
        frontApp,
        "teammateId",
      ],
      label: "Author ID",
      description: "ID of the teammate who is the author of the message. Ignored if the message is inbound.",
      optional: true,
    },
    to: {
      propDefinition: [
        frontApp,
        "to",
      ],
    },
    cc: {
      propDefinition: [
        frontApp,
        "cc",
      ],
    },
    bcc: {
      propDefinition: [
        frontApp,
        "bcc",
      ],
    },
    subject: {
      type: "string",
      label: "Subject",
      description: "Subject of the message.",
      optional: true,
    },
    body: {
      type: "string",
      label: "Body",
      description: "Body of the message.",
    },
    bodyFormat: {
      propDefinition: [
        frontApp,
        "bodyFormat",
      ],
    },
    externalId: {
      type: "string",
      label: "External ID",
      description: "External identifier of the message. Front won't import two messages with the same external ID.",
    },
    createdAt: {
      type: "integer",
      label: "Created At",
      description: "Date at which the message has been sent or received. A timestamp is expected as in `1655507769`",
      default: Math.floor(Date.now() / 1000),
    },
    type: {
      type: "string",
      label: "Type",
      description: "Type of the message to import. Can be one of: `email`, `sms`, `intercom`, `custom`. (Default: `email`)",
      optional: true,
      options: [
        "email",
        "sms",
        "intercom",
        "custom",
      ],
    },
    assigneeId: {
      propDefinition: [
        frontApp,
        "teammateId",
      ],
      label: "Assignee ID",
      description: "ID of the teammate who will be assigned to the conversation.",
      optional: true,
    },
    tags: {
      propDefinition: [
        frontApp,
        "tagIds",
      ],
      optional: true,
      description: "List of tag names to add to the conversation (unknown tags will automatically be created)",
    },
    threadRef: {
      propDefinition: [
        frontApp,
        "threadRef",
      ],
    },
    isInbound: {
      type: "boolean",
      label: "Is Inbound",
      description: "Whether or not the message is received (inbound) or sent (outbound) by you",
    },
    isArchive: {
      type: "boolean",
      label: "Is Archive",
      description: "Whether or not the message should be directly archived once imported. (Default: true)",
      optional: true,
    },
    shouldSkipRules: {
      type: "boolean",
      label: "Should Skip Rules",
      description: "Whether or not the rules should apply to this message. (Default: true)",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      inboxId,
      handle,
      name,
      authorId,
      subject,
      body,
      bodyFormat,
      externalId,
      createdAt,
      type,
      assigneeId,
      threadRef,
      isArchive,
      isInbound,
      shouldSkipRules,
    } = this;

    const to = utils.parse(this.to);
    const cc = utils.parse(this.cc);
    const bcc = utils.parse(this.bcc);
    const tags = utils.parse(this.tags);

    const data = {
      sender: {
        author_id: authorId,
        name,
        handle,
      },
      to,
      cc,
      bcc,
      subject,
      body,
      body_format: bodyFormat,
      external_id: externalId,
      created_at: createdAt,
      type,
      assignee_id: assigneeId,
      tags,
      metadata: {
        thread_ref: threadRef,
        is_inbound: isInbound,
        is_archived: isArchive,
        should_skip_rules: shouldSkipRules,
      },
    };

    const response =
      await this.frontApp.importMessage({
        inboxId,
        data,
      });

    const { message_uid: messageId } = response;

    $.export("$summary", `Successfully imported message with ID ${messageId}`);

    return response;
  },
};

Action Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

LabelPropTypeDescription
FrontfrontAppappThis component uses the Front app.
Inbox IDinboxIdstringSelect a value from the drop down menu.
Handlehandlestring

Handle used to reach the contact. Can be an email address, a twitter, handle, a phone number, custom handle ...

Namenamestring

Name of the contact.

Author IDauthorIdstringSelect a value from the drop down menu.
Totostring[]

List of recipient handles who received the message.

CCccstring[]

List of recipient handles who received a copy of the message.

BCCbccstring[]

List of the recipeient handles who received a blind copy of the message.

Subjectsubjectstring

Subject of the message.

Bodybodystring

Body of the message.

Body FormatbodyFormatstringSelect a value from the drop down menu:htmlmarkdown
External IDexternalIdstring

External identifier of the message. Front won't import two messages with the same external ID.

Created AtcreatedAtinteger

Date at which the message has been sent or received. A timestamp is expected as in 1655507769

TypetypestringSelect a value from the drop down menu:emailsmsintercomcustom
Assignee IDassigneeIdstringSelect a value from the drop down menu.
Tag IDstagsstring[]Select a value from the drop down menu.
Thread RefthreadRefstringSelect a value from the drop down menu.
Is InboundisInboundboolean

Whether or not the message is received (inbound) or sent (outbound) by you

Is ArchiveisArchiveboolean

Whether or not the message should be directly archived once imported. (Default: true)

Should Skip RulesshouldSkipRulesboolean

Whether or not the rules should apply to this message. (Default: true)

Action Authentication

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

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

About Front

Customer communication platform

More Ways to Connect Front + Google Drive

Send new message with Front API on Changes to Specific Files from Google Drive API
Google Drive + Front
 
Try it
Send new message with Front API on New Files (Instant) from Google Drive API
Google Drive + Front
 
Try it
Send new message with Front API on New or Modified Comments from Google Drive API
Google Drive + Front
 
Try it
Send new message with Front API on New or Modified Files from Google Drive API
Google Drive + Front
 
Try it
Send new message with Front API on New or Modified Folders from Google Drive API
Google Drive + Front
 
Try it
Changes to Specific Files from the Google Drive API

Watches for changes to specific files, emitting an event any time a change is made to one of those files. To watch for changes to shared drive files, use the Changes to Specific Files (Shared Drive) source instead.

 
Try it
Changes to Specific Files (Shared Drive) from the Google Drive API

Watches for changes to specific files in a shared drive, emitting an event any time a change is made to one of those files

 
Try it
New Files (Instant) from the Google Drive API

Emit new event any time a new file is added in your linked Google Drive

 
Try it
New or Modified Comments from the Google Drive API

Emits a new event any time a file comment is added, modified, or deleted in your linked Google Drive

 
Try it
New or Modified Files from the Google Drive API

Emit new event any time any file in your linked Google Drive is added, modified, or deleted

 
Try it
Add File Sharing Preference with the Google Drive API

Add a sharing permission to the sharing preferences of a file or folder and provide a sharing URL. See the docs for more information

 
Try it
Copy File with the Google Drive API

Create a copy of the specified file. See the docs for more information

 
Try it
Create a New File with the Google Drive API

Create a new file from a URL or /tmp/filepath. See the docs for more information

 
Try it
Create Folder with the Google Drive API

Create a new empty folder. See the docs for more information

 
Try it
Create New File From Template with the Google Drive API

Create a new Google Docs file from a template. Optionally include placeholders in the template document that will get replaced from this action. See documentation

 
Try it

Explore Other Apps

1
-
24
of
2,000+
apps by most popular

HTTP / Webhook
HTTP / Webhook
Get a unique URL where you can send HTTP or webhook requests
Notion
Notion
Notion is a new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
OpenAI (ChatGPT)
OpenAI (ChatGPT)
OpenAI is an AI research and deployment company with the mission to ensure that artificial general intelligence benefits all of humanity. They are the makers of popular models like ChatGPT, DALL-E, and Whisper.
Schedule
Schedule
Trigger workflows on an interval or cron schedule.
Google Drive
Google Drive
Google Drive is a file storage and synchronization service which allows you to create and share your work online, and access your documents from anywhere.
Google Sheets
Google Sheets
Use Google Sheets to create and edit online spreadsheets. Get insights together with secure sharing in real-time and from any device.
Filter
Filter
Specify a condition that your workflow must meet and whether you'd like to proceed or end workflow execution.
Python
Python
Anything you can do in Python can be done in a Pipedream Workflow. This includes using any of the 350,000+ PyPi packages available in your Python powered workflows.
Slack
Slack
Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.
Data Stores
Data Stores
Use Pipedream Data Stores to manage state throughout your workflows.
GitHub
GitHub
Where the world builds software. Millions of developers and companies build, ship, and maintain their software on GitHub—the largest and most advanced development platform in the world.
Formatting
Formatting
Pre-built actions to make formatting and manipulating data within your workflows easier.
Node
Node
Anything you can do with Node.js, you can do in a Pipedream workflow. This includes using most of npm's 400,000+ packages.
Airtable (OAuth)
Airtable (OAuth)
Airtable is a low-code platform to build next-gen apps. Move beyond rigid tools, operationalize your critical data, and reimagine workflows with AI.
Zoom
Zoom
Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars.
Google Calendar
Google Calendar
With Google Calendar, you can quickly schedule meetings and events and get reminders about upcoming activities, so you always know what’s next.
Gmail
Gmail
Gmail offers private and secure email by Google at no cost, for business and consumer accounts.
Gmail (Developer App)
Gmail (Developer App)
Private and secure email by Google at no cost, for business and consumer accounts. Use this app to connect your own developer account credentials.
Email
Email
Trigger workflows on new emails, and send emails to yourself as part of a Pipedream workflow.
Delay
Delay
Delay, pause, suspend, or have the execution of your workflow wait for as little as one millisecond, or as long as one year.
Go
Go
Anything you can do in Go, you can do in a Pipedream Workflow. You can use any of Go packages available with a simple import.
Premium
Zoom Admin
Zoom Admin
Video conferencing (includes account-level scopes) for Zoom Admins.
Twilio
Twilio
Twilio is a cloud communications platform for building SMS, Voice & Messaging applications on an API built for global scale.
Bash
Bash
Run any Bash in a Pipedream step within your workflow, including making curl requests.