Create Unique Lead with Vryno API on Changes to Specific Files (Shared Drive) from Google Drive API

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

Trigger workflow on

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

Next, do this

Create Unique Lead with the Vryno API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the Changes to Specific Files (Shared Drive) trigger
1. Connect your Google Drive account
2. Select a Drive
3. Configure Push notification renewal schedule
4. Select one or more Files
5. Configure intervalAlert
6. Optional- Configure Minimum Interval Per File
Configure the Create Unique Lead action
1. Connect your Vryno account
2. Optional- Configure First Name
3. Configure Last Name
4. Optional- Configure Email
5. Optional- Configure Phone Number
6. Optional- Configure Company
7. Optional- Configure Website
8. Configure Owner Id
9. Optional- Configure Score
10. Optional- Configure Expected Revenue
11. Optional- Configure Number Of Employees
12. Optional- Configure Billing Address
13. Optional- Configure Billing City
14. Optional- Configure Billing State
15. Optional- Configure Billing Country
16. Optional- Configure Billing Zipcode
17. Optional- Configure Shipping Address
18. Optional- Configure Shipping City
19. Optional- Configure Shipping State
20. Optional- Configure Shipping Country
21. Optional- Configure Shipping Zipcode
22. Optional- Configure Description
Deploy the workflow
Send a test event to validate your setup
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#

Changes to Specific Files (Shared Drive) on Google Drive

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

Version:0.2.6

Key:google_drive-changes-to-specific-files-shared-drive

View on GitHub

Google Drive Overview#

The Google Drive API on Pipedream allows you to automate various file management tasks, such as creating, reading, updating, and deleting files within your Google Drive. You can also share files, manage permissions, and monitor changes to files and folders. This opens up possibilities for creating workflows that seamlessly integrate with other apps and services, streamlining document handling, backup processes, and collaborative workflows.

Trigger Code#

// This source processes changes to specific files in a user's Google Drive,
// implementing strategy enumerated in the Push Notifications API docs:
// https://developers.google.com/drive/api/v3/push .
//
// This source has two interfaces:
//
// 1) The HTTP requests tied to changes in files 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 sampleEmit from "./test-event.mjs";

import {
  GOOGLE_DRIVE_NOTIFICATION_CHANGE,
  GOOGLE_DRIVE_NOTIFICATION_ADD,
  GOOGLE_DRIVE_NOTIFICATION_UPDATE,
} from "../../common/constants.mjs";
import commonDedupeChanges from "../common-dedupe-changes.mjs";

/**
 * This source uses the Google Drive API's
 * {@link https://developers.google.com/drive/api/v3/reference/changes/watch changes: watch}
 * endpoint to subscribe to changes to the user's drive or a shard drive.
 */
export default {
  ...common,
  key: "google_drive-changes-to-specific-files-shared-drive",
  name: "Changes to Specific Files (Shared Drive)",
  description: "Watches for changes to specific files in a shared drive, emitting an event when a change is made to one of those files",
  version: "0.2.6",
  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: {
    ...common.props,
    files: {
      type: "string[]",
      label: "Files",
      description: "The files you want to watch for changes.",
      options({ prevContext }) {
        const { nextPageToken } = prevContext;
        return this.googleDrive.listFilesOptions(nextPageToken, this.getListFilesOpts());
      },
    },
    ...commonDedupeChanges.props,
  },
  hooks: {
    async deploy() {
      const daysAgo = new Date();
      daysAgo.setDate(daysAgo.getDate() - 30);
      const timeString = daysAgo.toISOString();

      const args = this.getListFilesOpts({
        q: `mimeType != "application/vnd.google-apps.folder" and modifiedTime > "${timeString}" and trashed = false`,
        fields: "files",
        pageSize: 5,
      });

      const { files } = await this.googleDrive.listFilesInPage(null, args);

      this.processChanges(files);
    },
    ...common.hooks,
  },
  methods: {
    ...common.methods,
    getUpdateTypes() {
      return [
        GOOGLE_DRIVE_NOTIFICATION_ADD,
        GOOGLE_DRIVE_NOTIFICATION_CHANGE,
        GOOGLE_DRIVE_NOTIFICATION_UPDATE,
      ];
    },
    generateMeta(data, headers) {
      const {
        id: fileId,
        name: fileName,
        modifiedTime: tsString,
      } = data;
      const ts = Date.parse(tsString);
      const eventId = headers && headers["x-goog-message-number"];
      const resourceState = headers && headers["x-goog-resource-state"];

      const summary = resourceState
        ? `${resourceState.toUpperCase()} - ${fileName || "Untitled"}`
        : fileName || "Untitled";

      return {
        id: `${fileId}-${eventId || ts}`,
        summary,
        ts,
      };
    },
    isFileRelevant(file) {
      return this.files.includes(file.id);
    },
    getChanges(headers) {
      if (!headers) {
        return {
          change: { },
        };
      }
      return {
        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"
        },
      };
    },
    processChange(file, headers) {
      const changes = this.getChanges(headers);
      const eventToEmit = {
        file,
        ...changes,
      };
      const meta = this.generateMeta(file, headers);
      this.$emit(eventToEmit, meta);
    },
    processChanges(changedFiles, headers) {
      console.log(`Processing ${changedFiles.length} changed files`);
      console.log(`Changed files: ${JSON.stringify(changedFiles, null, 2)}!!!`);
      console.log(`Files: ${this.files}!!!`);

      const filteredFiles = this.checkMinimumInterval(changedFiles);
      for (const file of filteredFiles) {
        if (!this.isFileRelevant(file)) {
          console.log(`Skipping event for irrelevant file ${file.id}`);
          continue;
        }
        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.

Label	Prop	Type	Description
Google Drive	`googleDrive`	`app`	This component uses the Google Drive app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.interface.http`	This 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.
Drive	`drive`	`string`	Select a value from the drop down menu.
Files	`files`	`string[]`	Select a value from the drop down menu.
Minimum Interval Per File	`perFileInterval`	`integer`	How many minutes to wait until the same file can emit another event. If set to `0`, this interval is disabled and all events will be emitted.

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:

https://www.googleapis.com/auth/drive

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#

Create Unique Lead on Vryno

Description:Creates a unique lead in the Vryno system, ensuring no duplication of lead details. [See the documentation](https://vrynotest.ti2.in/docs/api-documentation/how-to-create-a-record-in-any-module-in-vryno-crm/)

Version:0.0.1

Key:vryno-create-unique-lead

View on GitHub

Vryno Overview#

The Vryno API provides functionality to access a platform that specializes in various services including but not limited to real estate, healthcare, and educational services. By integrating this API into Pipedream workflows, developers can automate interactions and data exchanges between Vryno and other platforms, enhancing efficiency and enabling innovative service delivery models.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import vryno from "../../vryno.app.mjs";

export default {
  key: "vryno-create-unique-lead",
  name: "Create Unique Lead",
  description: "Creates a unique lead in the Vryno system, ensuring no duplication of lead details. [See the documentation](https://vrynotest.ti2.in/docs/api-documentation/how-to-create-a-record-in-any-module-in-vryno-crm/)",
  version: "0.0.1",
  type: "action",
  props: {
    vryno,
    firstName: {
      type: "string",
      label: "First Name",
      description: "The lead's first name.",
      optional: true,
    },
    name: {
      type: "string",
      label: "Last Name",
      description: "The lead's last name.",
    },
    email: {
      type: "string",
      label: "Email",
      description: "The lead's email.",
      optional: true,
    },
    phoneNumber: {
      type: "string",
      label: "Phone Number",
      description: "The lead's phone number.",
      optional: true,
    },
    company: {
      type: "string",
      label: "Company",
      description: "The company the lead works for.",
      optional: true,
    },
    website: {
      type: "string",
      label: "Website",
      description: "The lead's website.",
      optional: true,
    },
    ownerId: {
      type: "string",
      label: "Owner Id",
      description: "The user Id related to the lead.You can find the user IDs in your account -> settings -> users & controls -> users, click on some user and the ID will be in URL.",
    },
    score: {
      type: "integer",
      label: "Score",
      description: "The lead's score.",
      optional: true,
    },
    expectedRevenue: {
      type: "integer",
      label: "Expected Revenue",
      description: "Expected revenue for the lead.",
      optional: true,
    },
    numberOfEmployees: {
      type: "integer",
      label: "Number Of Employees",
      description: "Number of employees at the lead company.",
      optional: true,
    },
    billingAddress: {
      type: "string",
      label: "Billing Address",
      description: "The lead's billing address.",
      optional: true,
    },
    billingCity: {
      type: "string",
      label: "Billing City",
      description: "The lead's billing city.",
      optional: true,
    },
    billingState: {
      type: "string",
      label: "Billing State",
      description: "The lead's billing state.",
      optional: true,
    },
    billingCountry: {
      type: "string",
      label: "Billing Country",
      description: "The lead's billing country.",
      optional: true,
    },
    billingZipcode: {
      type: "string",
      label: "Billing Zipcode",
      description: "The lead's billing zipcode",
      optional: true,
    },
    shippingAddress: {
      type: "string",
      label: "Shipping Address",
      description: "The lead's shipping address.",
      optional: true,
    },
    shippingCity: {
      type: "string",
      label: "Shipping City",
      description: "The lead's shipping city.",
      optional: true,
    },
    shippingState: {
      type: "string",
      label: "Shipping State",
      description: "The lead's shipping state.",
      optional: true,
    },
    shippingCountry: {
      type: "string",
      label: "Shipping Country",
      description: "The lead's shipping country.",
      optional: true,
    },
    shippingZipcode: {
      type: "string",
      label: "Shipping Zipcode",
      description: "The lead's shipping zipcode",
      optional: true,
    },
    description: {
      type: "string",
      label: "Description",
      description: "A brief description about the lead.",
      optional: true,
    },
  },
  async run({ $ }) {
    if (!this.email && !this.phoneNumber) {
      throw new ConfigurationError("You must provide at least either **Email** or **Phone Number**.");
    }
    const duplicateCheck = await this.vryno.post({
      data: {
        query: `query {
          fetchLead(filters:[${this.email
    ? `{name: "email", operator:"eq",value:["${this.email}"]},`
    : ""}${this.phoneNumber
  ? `{name: "phoneNumber", operator:"eq",value:["${this.phoneNumber}"]}`
  : ""}],
  expression:"( ( a ) and b)"){
                code
                status
                message
                messageKey
                count
                data {
                  id
                } 
            }
        }`,
      },
    });

    if (duplicateCheck.data?.fetchLead?.data?.length) {
      $.export("$summary", "A lead with the same email and phone number already exists.");
      return duplicateCheck.data;
    }

    const {
      vryno,
      ...data
    } = this;

    let query = `mutation {
      createLead(input: {
        `;

    for (const [
      field,
      value,
    ] of Object.entries(data)) {
      query += `${field}:`;
      if ([
        "score",
        "expectedRevenue",
        "numberOfEmployees",
      ].includes(field)) {
        query += ` ${value}
        `;
      } else {
        query += ` "${value}"
        `;
      }
    }

    query += `}) {
        code
        message
        status
        messageKey
        data {
          id
        }
        errors
      }
    }`;

    const response = await vryno.post({
      $,
      data: {
        query,
      },
    });

    if (response.data.createLead.code != 200) {
      throw new ConfigurationError(response.data.createLead.message);
    }

    $.export("$summary", `Successfully created new lead with Id: ${response.data.createLead.data.id}`);
    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.

Label	Prop	Type	Description
Vryno	`vryno`	`app`	This component uses the Vryno app.
First Name	`firstName`	`string`	The lead's first name.
Last Name	`name`	`string`	The lead's last name.
Email	`email`	`string`	The lead's email.
Phone Number	`phoneNumber`	`string`	The lead's phone number.
Company	`company`	`string`	The company the lead works for.
Website	`website`	`string`	The lead's website.
Owner Id	`ownerId`	`string`	The user Id related to the lead.You can find the user IDs in your account -> settings -> users & controls -> users, click on some user and the ID will be in URL.
Score	`score`	`integer`	The lead's score.
Expected Revenue	`expectedRevenue`	`integer`	Expected revenue for the lead.
Number Of Employees	`numberOfEmployees`	`integer`	Number of employees at the lead company.
Billing Address	`billingAddress`	`string`	The lead's billing address.
Billing City	`billingCity`	`string`	The lead's billing city.
Billing State	`billingState`	`string`	The lead's billing state.
Billing Country	`billingCountry`	`string`	The lead's billing country.
Billing Zipcode	`billingZipcode`	`string`	The lead's billing zipcode
Shipping Address	`shippingAddress`	`string`	The lead's shipping address.
Shipping City	`shippingCity`	`string`	The lead's shipping city.
Shipping State	`shippingState`	`string`	The lead's shipping state.
Shipping Country	`shippingCountry`	`string`	The lead's shipping country.
Shipping Zipcode	`shippingZipcode`	`string`	The lead's shipping zipcode
Description	`description`	`string`	A brief description about the lead.

Action Authentication#

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

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

openidvryno_offline_access

About Vryno#

Powerful CRM System for a Fraction of Price. Vryno is a powerful CRM system that has been meticulously crafted to cater to the evolving needs of modern businesses.

More Ways to Connect Vryno + Google Drive#

Other Popular Integrations#

Create Unique Lead with Vryno API on New Presentation (Instant) from Google Drive API

Google Drive + Vryno

Create Unique Lead with Vryno API on Changes to Specific Files (Shared Drive) from Google Drive API

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

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

Developers ♥ Pipedream

1-24of2,700+apps by most popular

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