Create Unique Lead with Vryno API on New Scheduled Tasks from Pipedream API

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

Trigger workflow on

New Scheduled Tasks from the Pipedream 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 Pipedream 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 New Scheduled Tasks trigger
1. Connect your Pipedream account
2. Optional- Configure Secret
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#

New Scheduled Tasks on Pipedream

Description:Exposes an HTTP API for scheduling messages to be emitted at a future time

Version:0.3.1

Key:pipedream-new-scheduled-tasks

View on GitHub

Pipedream Overview#

Pipedream is an API that allows you to build applications that can connect to
various data sources and processes them in real-time. You can use Pipedream to
create applications that can perform ETL (Extract, Transform, and Load) tasks,
as well as to create data-driven workflows.

Some examples of applications you can build using the Pipedream API include:

An application that can extract data from a database, transform it, and then
load it into another database.
An application that can monitor a data source for changes, and then trigger a
workflow in response to those changes.
An application that can poll an API for new data, and then process that data
in real-time.

Trigger Code#

import pipedream from "../../pipedream.app.mjs";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";

export default {
  key: "pipedream-new-scheduled-tasks",
  name: "New Scheduled Tasks",
  type: "source",
  description:
    "Exposes an HTTP API for scheduling messages to be emitted at a future time",
  version: "0.3.1",
  dedupe: "unique", // Dedupe on a UUID generated for every scheduled task
  props: {
    pipedream,
    secret: {
      type: "string",
      secret: true,
      label: "Secret",
      optional: true,
      description:
        "**Optional but recommended**: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests",
    },
    http: {
      label: "Endpoint",
      description: "The endpoint where you'll send task scheduler requests",
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
  },
  methods: {
    // To schedule future emits, we emit to the selfChannel of the component
    selfChannel() {
      return "self";
    },
    // Queue for future emits that haven't yet been delivered
    queuedEventsChannel() {
      return "$in";
    },
    httpRespond({
      status, body,
    }) {
      this.http.respond({
        headers: {
          "content-type": "application/json",
        },
        status,
        body,
      });
    },
    async selfSubscribe() {
      // Subscribe the component to itself. We do this here because even in
      // the activate hook, the component isn't available to take subscriptions.
      // Scheduled tasks are sent to the self channel, which emits the message at
      // the specified delivery_ts to this component.
      const isSubscribedToSelf = this.db.get("isSubscribedToSelf");
      if (!isSubscribedToSelf) {
        const componentId = process.env.PD_COMPONENT;
        const selfChannel = this.selfChannel();
        console.log(`Subscribing to ${selfChannel} channel for event source`);
        console.log(
          await this.pipedream.subscribe(componentId, componentId, selfChannel),
        );
        this.db.set("isSubscribedToSelf", true);
      }
    },
    validateEventBody(event, operation) {
      const errors = [];

      // Secrets are optional, so we first check if the user configured
      // a secret, then check its value against the prop (validation below)
      if (this.secret && event.headers["x-pd-secret"] !== this.secret) {
        errors.push(
          "Secret on incoming request doesn't match the configured secret",
        );
      }

      if (operation === "schedule") {
        const {
          timestamp,
          message,
        } = event.body;
        // timestamp should be an ISO 8601 string. Parse and check for validity below.
        const epoch = Date.parse(timestamp);

        if (!timestamp) {
          errors.push(
            "No timestamp included in payload. Please provide an ISO8601 timestamp in the 'timestamp' field",
          );
        }
        if (timestamp && !epoch) {
          errors.push("Timestamp isn't a valid ISO 8601 string");
        }
        if (!message) {
          errors.push("No message passed in payload");
        }
      }

      return errors;
    },
    scheduleTask(event) {
      const errors = this.validateEventBody(event, "schedule");
      let status, body;

      if (errors.length) {
        console.log(errors);
        status = 400;
        body = {
          errors,
        };
      } else {
        const id = this.emitScheduleEvent(event.body, event.body.timestamp);
        status = 200;
        body = {
          msg: "Successfully scheduled task",
          id,
        };
      }

      this.httpRespond({
        status,
        body,
      });
    },
    emitScheduleEvent(event, timestamp) {
      const selfChannel = this.selfChannel();
      const epoch = Date.parse(timestamp);
      const $id = uuid();

      console.log(`Scheduled event to emit on: ${new Date(epoch)}`);

      this.$emit(
        {
          ...event,
          $channel: selfChannel,
          $id,
        },
        {
          name: selfChannel,
          id: $id,
          delivery_ts: epoch,
        },
      );

      return $id;
    },
    async cancelTask(event) {
      const errors = this.validateEventBody(event, "cancel");
      let status, msg;

      if (errors.length) {
        console.log(errors);
        status = 400;
        msg = "Secret on incoming request doesn't match the configured secret";
      } else {
        try {
          const id = event.body.id;
          const isCanceled = await this.deleteEvent(event);
          if (isCanceled) {
            status = 200;
            msg = `Cancelled scheduled task for event ${id}`;
          } else {
            status = 404;
            msg = `No event with ${id} found`;
          }
        } catch (error) {
          console.log(error);
          status = 500;
          msg = "Failed to schedule task. Please see the logs";
        }
      }

      this.httpRespond({
        status,
        body: {
          msg,
        },
      });
    },
    async deleteEvent(event) {
      const componentId = process.env.PD_COMPONENT;
      const inChannel = this.queuedEventsChannel();

      // The user must pass a scheduled event UUID they'd like to cancel
      // We lookup the event by ID and delete it
      const { id } = event.body;

      // List events in the $in channel - the queue of scheduled events, to be emitted in the future
      const events = await this.pipedream.listEvents(
        componentId,
        inChannel,
      );
      console.log("Events: ", events);

      // Find the event in the list by id
      const eventToCancel = events.data.find((e) => {
        const { metadata } = e;
        return metadata.id === id;
      });

      console.log("Event to cancel: ", eventToCancel);

      if (!eventToCancel) {
        console.log(`No event with ${id} found`);
        return false;
      }

      // Delete the event
      await this.pipedream.deleteEvent(
        componentId,
        eventToCancel.id,
        inChannel,
      );
      return true;
    },
    emitEvent(event, summary) {
      // Delete the channel name and id from the incoming event, which were used only as metadata
      const id = event.$id;
      delete event.$channel;
      delete event.$id;

      this.$emit(event, {
        summary: summary ?? JSON.stringify(event),
        id,
        ts: +new Date(),
      });
    },
  },
  async run(event) {
    await this.selfSubscribe();

    const { path } = event;
    if (path === "/schedule") {
      this.scheduleTask(event);
    } else if (path === "/cancel") {
      await this.cancelTask(event);
    } else if (event.$channel === this.selfChannel()) {
      this.emitEvent(event);
    }
  },
  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
Pipedream	`pipedream`	`app`	This component uses the Pipedream app.
Secret	`secret`	`string`	Optional but recommended: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests
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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

Pipedream uses API keys for authentication. When you connect your Pipedream account, Pipedream securely stores the keys so you can easily authenticate to Pipedream APIs in both code and no-code steps.

About Pipedream#

Integration platform for developers

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 + Pipedream#

Popular Triggers#

New Scheduled Tasks from the Pipedream API

Exposes an HTTP API for scheduling messages to be emitted at a future time

Try it

New Upcoming Event Alert from the Pipedream API

Emit new event based on a time interval before an upcoming event in the calendar. This source uses Pipedream's Task Scheduler. See the documentation for more information and instructions for connecting your Pipedream account.

Try it

Card Due Date Reminder from the Pipedream API

Emit new event at a specified time before a card is due.

Try it

New Upcoming Calendar Event from the Pipedream API

Emit new event when a Calendar event is upcoming, this source is using reminderMinutesBeforeStart property of the event to determine the time it should emit.

Try it