Create Unique Lead with Vryno API on New Events (Instant) from Twilio SendGrid API

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

Trigger workflow on

New Events (Instant) from the Twilio SendGrid 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 Twilio SendGrid 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 Events (Instant) trigger
1. Connect your Twilio SendGrid account
2. Select one or more Event Types
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 Events (Instant) on Twilio SendGrid

Description:Emit new event when any of the specified SendGrid events is received

Version:0.0.6

Key:sendgrid-events

View on GitHub

Twilio SendGrid Overview#

The Twilio SendGrid API opens up a world of possibilities for email automation, enabling you to send emails efficiently and track their performance. With this API, you can programmatically create and send personalized email campaigns, manage contacts, and parse inbound emails for data extraction. When you harness the power of Pipedream, you can connect SendGrid to hundreds of other apps to automate workflows, such as triggering email notifications based on specific actions, syncing email stats with your analytics, or handling incoming emails to create tasks or tickets.

Trigger Code#

import common from "../common/http-based.mjs";
import deliveryEventTypes from "./delivery-event-types.mjs";
import engagementEventTypes from "./engagement-event-types.mjs";

export default {
  ...common,
  key: "sendgrid-events",
  name: "New Events (Instant)",
  description: "Emit new event when any of the specified SendGrid events is received",
  version: "0.0.6",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    eventTypes: {
      type: "string[]",
      label: "Event Types",
      description: "The type of events to listen to",
      options(context) {
        const { page } = context;
        if (page !== 0) {
          return {
            options: [],
          };
        }

        const options = [
          ...deliveryEventTypes,
          ...engagementEventTypes,
        ];
        return {
          options,
        };
      },
    },
  },
  methods: {
    ...common.methods,
    baseWebhookSettings() {
      // The list of events that a webhook can listen to. This method returns an
      // exhaustive list of all such flags disabled, and each event source can
      // then override the flags that are relevant to the event they handle.
      //
      // See the docs for more information:
      // https://sendgrid.com/docs/api-reference/
      const eventTypesData = [
        ...deliveryEventTypes,
        ...engagementEventTypes,
      ];
      return eventTypesData.reduce((accum, eventTypeData) => ({
        ...accum,
        [eventTypeData.value]: false,
      }), {});
    },
    webhookEventFlags() {
      return this.eventTypes.reduce((accum, eventType) => ({
        ...accum,
        [eventType]: true,
      }), {});
    },
    generateMeta(data) {
      const {
        event: eventType,
        sg_event_id: id,
        timestamp: ts,
      } = data;
      const summary = `New event: ${eventType}`;
      return {
        id,
        summary,
        ts,
      };
    },
  },
};

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
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Twilio SendGrid	`sendgrid`	`app`	This component uses the Twilio SendGrid app.
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.
Event Types	`eventTypes`	`string[]`	Select a value from the drop down menu.

Trigger Authentication#

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

About Twilio SendGrid#

Send marketing and transactional email through the Twilio SendGrid platform with the Email API, proprietary mail transfer agent, and infrastructure for scalable delivery.

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