Enrich a person with People Data Labs API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for People Data Labs, HTTP / Webhook and 2,000+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Enrich a person with the People Data Labs API

No credit card required

▶

Watch us build a workflow

4 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook 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 Requests trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
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 Requests on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

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

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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	`httpInterface`	`$.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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

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#

People Data Labs API provides reliable access to massive and up-to-date
worldwide datasets, enabling businesses to get the data they need to make more
informed decisions. With People Data Labs' easy-to-use API, you can explore and
access a variety of datasets to build innovative solutions. Here are a few
examples of what you can build using the People Data Labs API:

Build comprehensive people profiles using data from a variety of sources,
including public records, job history, digital identities, and more.
Create dynamic user segmentation tools to better target and engage with
customers.
Provide sophisticated background checks for due diligence and fraud
detection.
Create predictive models for developing valuable insights on consumer
behavior.
Generate powerful analytics by blending different datasets to uncover
patterns and trends.
Create decision-making tools to improve recruitment and onboarding processes.
Develop powerful lead generation & retargeting tools to drive more sales.
Develop apps that automatically surface the most relevant personal
information for tasks.

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.

Action Authentication#

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

Signup for an API key. Upon sign in, API Key, along with a few example API calls appear in the dashboard.

About People Data Labs#

The source of the truth for person data