Enrich a person with People Data Labs API on New, Updated, or Deleted Warehouse from Snowflake API

Pipedream makes it easy to connect APIs for People Data Labs, Snowflake and 2,400+ other apps remarkably fast.

Trigger workflow on

New, Updated, or Deleted Warehouse from the Snowflake API

Next, do this

Enrich a person with the People Data Labs 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 Snowflake trigger and People Data Labs action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New, Updated, or Deleted Warehouse trigger
1. Connect your Snowflake account
2. Configure timer
3. Optional- Select one or more Query Types
4. Optional- Select one or more Warehouse Name
Configure the Enrich a person action
1. Connect your People Data Labs account
2. Optional- Configure Name
3. Optional- Configure First name
4. Optional- Configure Last name
5. Optional- Configure Middle name
6. Optional- Configure Location
7. Optional- Configure Street address
8. Optional- Configure Locality
9. Optional- Configure Region
10. Optional- Configure Country
11. Optional- Configure Postal code
12. Optional- Configure Company
13. Optional- Configure School
14. Optional- Configure Phone
15. Optional- Configure Email
16. Optional- Configure Email hash
17. Optional- Configure Profile
18. Optional- Configure Linkedin ID
19. Optional- Configure Birth date
20. Optional- Configure Required
21. Optional- Configure Pretty
22. Optional- Configure Min Likelihood
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, Updated, or Deleted Warehouse on Snowflake

Description:Emit new events when a warehouse is created, altered, or dropped

Version:0.1.2

Key:snowflake-change-to-warehouse

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

import common from "../common-watch-for-resource-changes.mjs";

export default {
  ...common,
  props: {
    ...common.props,
    warehouses: {
      propDefinition: [
        common.props.snowflake,
        "warehouses",
      ],
      optional: true,
    },
  },
  type: "source",
  key: "snowflake-change-to-warehouse",
  // eslint-disable-next-line
  name: "New, Updated, or Deleted Warehouse",
  description: "Emit new events when a warehouse is created, altered, or dropped",
  version: "0.1.2",
  async run() {
    await this.watchObjectsAndEmitChanges("WAREHOUSE", this.warehouses, this.queryTypes);
  },
};

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
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Watch for changes on this schedule. Snowflake query history has roughly a 45 minute delay
Query Types	`queryTypes`	`string[]`	Select a value from the drop down menu:`CREATEALTERDROP`
Warehouse Name	`warehouses`	`string[]`	Select a value from the drop down menu.

Trigger Authentication#

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

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

Action#

Enrich a person on People Data Labs

Description:The Person Enrichment API provides a one-to-one match, retrieving up-to-date information on a unique individual. [See the docs here](https://docs.peopledatalabs.com/docs/reference-person-enrichment-api)

Version:0.0.4

Key:people_data_labs-enrich-person

View on GitHub

People Data Labs Overview#

The People Data Labs API provides access to a rich database of profiles, offering granular data on individuals such as employment history, education, skills, and more. Leveraging Pipedream's capabilities, you can automate personalized outreach, enrich contact lists, validate professional information, and sync data across platforms in real-time. These automations can power recruitment, sales, and networking efforts by providing up-to-date and comprehensive data points.

Action Code#

import app from "../../people_data_labs.app.mjs";

export default {
  key: "people_data_labs-enrich-person",
  name: "Enrich a person",
  description: "The Person Enrichment API provides a one-to-one match, retrieving up-to-date information on a unique individual. [See the docs here](https://docs.peopledatalabs.com/docs/reference-person-enrichment-api)",
  version: "0.0.4",
  type: "action",
  props: {
    app,
    name: {
      label: "Name",
      type: "string",
      description: "The person's full name, at least first and last.",
      optional: true,
    },
    firstName: {
      label: "First name",
      type: "string",
      description: "The person's first name.",
      optional: true,
    },
    lastName: {
      label: "Last name",
      type: "string",
      description: "The person's last name.",
      optional: true,
    },
    middleName: {
      label: "Middle name",
      type: "string",
      description: "The person's middle name.",
      optional: true,
    },
    location: {
      label: "Location",
      type: "string",
      description: "The location in which a person lives. Can be anything from a street address to a country name.",
      optional: true,
    },
    streetAddress: {
      label: "Street address",
      type: "string",
      description: "A street address in which the person lives.",
      optional: true,
    },
    locality: {
      label: "Locality",
      type: "string",
      description: "A locality in which the person lives.",
      optional: true,
    },
    region: {
      label: "Region",
      type: "string",
      description: "A state or region in which the person lives.",
      optional: true,
    },
    country: {
      label: "Country",
      type: "string",
      description: "A country in which the person lives.",
      optional: true,
    },
    postalCode: {
      label: "Postal code",
      type: "string",
      description: "The postal code in which the person lives, must be used with either a country or a region.",
      optional: true,
    },
    company: {
      label: "Company",
      type: "string",
      description: "A name, website, or social url of a company where the person has worked.",
      optional: true,
    },
    school: {
      label: "School",
      type: "string",
      description: "A name, website, or social url of a university or college the person has attended.",
      optional: true,
    },
    phone: {
      label: "Phone",
      type: "string",
      description: "A phone number the person has used.",
      optional: true,
    },
    email: {
      label: "Email",
      type: "string",
      description: "An email the person has used.",
      optional: true,
    },
    emailHash: {
      label: "Email hash",
      type: "string",
      description: "A sha256 email hash.",
      optional: true,
    },
    profile: {
      label: "Profile",
      type: "string",
      description: "A social profile the person has used. [List of available social profiles](https://docs.peopledatalabs.com/docs/social-networks).",
      optional: true,
    },
    lid: {
      label: "Linkedin ID",
      type: "integer",
      description: "A LinkedIn numerical ID.",
      optional: true,
    },
    birthDate: {
      label: "Birth date",
      type: "string",
      description: "The person's birth date. Either the year, or a full birth date.",
      optional: true,
    },
    required: {
      label: "Required",
      type: "string",
      description: "Parameter specifying the fields and data points a response must have to return a 200. [See docs](https://docs.peopledatalabs.com/docs/required-parameter).",
      optional: true,
    },
    pretty: {
      propDefinition: [
        app,
        "pretty",
      ],
    },
    minLikelihood: {
      propDefinition: [
        app,
        "minLikelihood",
      ],
    },
  },
  async run({ $ }) {
    const params = {
      name: this.name,
      first_name: this.firstName,
      last_name: this.lastName,
      middle_name: this.middleName,
      location: this.location,
      street_address: this.streetAddress,
      locality: this.locality,
      region: this.region,
      country: this.country,
      postal_code: this.postalCode,
      company: this.company,
      school: this.school,
      phone: this.phone,
      email: this.email,
      email_hash: this.emailHash,
      profile: this.profile,
      lid: this.lid,
      birth_date: this.birthDate,
      min_likelihood: this.minLikelihood || 0,
      required: this.required,
      pretty: this.pretty || true,
    };

    const res = await this.app.enrichPerson({
      $,
      params,
    });
    if (!res) {
      $.export("$summary", "No results found");
    } else {
      $.export("$summary", "Successfully enriched a person");
    }
    return res;
  },
};

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
People Data Labs	`app`	`app`	This component uses the People Data Labs app.
Name	`name`	`string`	The person's full name, at least first and last.
First name	`firstName`	`string`	The person's first name.
Last name	`lastName`	`string`	The person's last name.
Middle name	`middleName`	`string`	The person's middle name.
Location	`location`	`string`	The location in which a person lives. Can be anything from a street address to a country name.
Street address	`streetAddress`	`string`	A street address in which the person lives.
Locality	`locality`	`string`	A locality in which the person lives.
Region	`region`	`string`	A state or region in which the person lives.
Country	`country`	`string`	A country in which the person lives.
Postal code	`postalCode`	`string`	The postal code in which the person lives, must be used with either a country or a region.
Company	`company`	`string`	A name, website, or social url of a company where the person has worked.
School	`school`	`string`	A name, website, or social url of a university or college the person has attended.
Phone	`phone`	`string`	A phone number the person has used.
Email	`email`	`string`	An email the person has used.
Email hash	`emailHash`	`string`	A sha256 email hash.
Profile	`profile`	`string`	A social profile the person has used. List of available social profiles.
Linkedin ID	`lid`	`integer`	A LinkedIn numerical ID.
Birth date	`birthDate`	`string`	The person's birth date. Either the year, or a full birth date.
Required	`required`	`string`	Parameter specifying the fields and data points a response must have to return a 200. See docs.
Pretty	`pretty`	`boolean`	Whether the output should have human-readable indentation.
Min Likelihood	`minLikelihood`	`integer`	The minimum likelihood score a response must have to return a 200.