Create Unique Lead with Vryno API on New Row Custom Query from PostgreSQL API

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

Trigger workflow on

New Row Custom Query from the PostgreSQL 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 PostgreSQL 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 Row Custom Query trigger
1. Connect your PostgreSQL account
2. Configure Polling Interval
3. Select a Schema
4. Select a Table
5. Select a Column
6. Configure SQL Query
7. Optional- Configure Values
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 Row Custom Query on PostgreSQL

Description:Emit new event when new rows are returned from a custom query that you provide. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.6

Key:postgresql-new-row-custom-query

View on GitHub

PostgreSQL Overview#

On Pipedream, you can leverage the PostgreSQL app to create workflows that automate database operations, synchronize data across platforms, and react to database events in real-time. Think handling new row entries, updating records from webhooks, or even compiling reports on a set schedule. Pipedream's serverless platform provides a powerful way to connect PostgreSQL with a variety of apps, enabling you to create tailored automation that fits your specific needs.

Trigger Code#

import common from "../common.mjs";

export default {
  ...common,
  name: "New Row Custom Query",
  key: "postgresql-new-row-custom-query",
  description: "Emit new event when new rows are returned from a custom query that you provide. [See the documentation](https://node-postgres.com/features/queries)",
  version: "2.0.6",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    schema: {
      propDefinition: [
        common.props.postgresql,
        "schema",
      ],
    },
    table: {
      propDefinition: [
        common.props.postgresql,
        "table",
        (c) => ({
          schema: c.schema,
        }),
      ],
    },
    column: {
      propDefinition: [
        common.props.postgresql,
        "column",
        (c) => ({
          table: c.table,
          schema: c.schema,
        }),
      ],
    },
    query: {
      propDefinition: [
        common.props.postgresql,
        "query",
      ],
    },
    values: {
      propDefinition: [
        common.props.postgresql,
        "values",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateMeta(row, column) {
      return {
        id: row[column],
        summary: "New Row",
        ts: Date.now(),
      };
    },
  },
  async run() {
    const {
      schema,
      table,
      column,
      query,
      values = [],
    } = this;

    if (!Array.isArray(values)) {
      throw new Error("No valid values provided. The values property must be an array.");
    }

    const numberOfValues = query?.match(/\$/g)?.length || 0;
    if (values.length !== numberOfValues) {
      throw new Error("The number of values provided does not match the number of values in the query.");
    }

    const isColumnUnique = await this.isColumnUnique(schema, table, column);
    if (!isColumnUnique) {
      throw new Error("The column selected contains duplicate values. Column must be unique");
    }

    const rows = await this.postgresql.executeQuery({
      text: query,
      values,
    });
    for (const row of rows) {
      const meta = this.generateMeta(row, column);
      this.$emit(row, meta);
    }
  },
};

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
PostgreSQL	`postgresql`	`app`	This component uses the PostgreSQL app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling Interval	`timer`	`$.interface.timer`	Pipedream will poll the API on this schedule
Schema	`schema`	`string`	Select a value from the drop down menu.
Table	`table`	`string`	Select a value from the drop down menu.
Column	`column`	`string`	Select a value from the drop down menu.
SQL Query	`query`	`string`	Your custom SQL Query using `$1`, `$2`... to represent values (eg. `INSERT INTO users(name, email) VALUES($1, $2)`
Values	`values`	`string[]`	List of values represented in your SQL Query above

Trigger Authentication#

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

Connecting to Restricted Databases

Either enable the shared static IP for this account below, or configure a VPC to deploy any workflow in your workspace to a private network with a dedicated static IP. Learn more in our docs.

SSL Setup

Configure SSL on your PostgreSQL database by providing the CA (Certificate Authority), and choosing between Full Verification, Verify Certificate Authority (CA), or Skip Verification. Skipping verification is not recommended as this has serious security implications.

About PostgreSQL#

PostgreSQL is a free and open-source relational database management system emphasizing extensibility and SQL compliance.

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