People Data Labs: Person Search

Search people with structured filters or SQL over job title, company, location, and skills.

Tool ID: peopledatalabs_person_search

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'peopledatalabs_person_search',
  {
    "query": {},
    "sql": "SELECT * FROM person WHERE location_country=\"united states\" AND job_title_role=\"engineering\"",
    "size": 123
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute peopledatalabs_person_search --input '{
  "query": {},
  "sql": "SELECT * FROM person WHERE location_country=\"united states\" AND job_title_role=\"engineering\"",
  "size": 123
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "data": [
      {}
    ],
    "total": 123,
    "scroll_token": "example"
  }
}

Use deepline tools get peopledatalabs_person_search --json for the latest machine-readable contract.

Input reference

People Data Labs person search input.

Name	Type	Required	Default	Details
`payload.query`	`record`	No	—	Elasticsearch-style query. Use this OR `sql`, not both. If you are unsure about field names, prefer `sql` with known fields.
`payload.sql`	`string`	No	—	SQL must be in the form `SELECT * FROM person WHERE ...`. Use single quotes for string literals (e.g., name=‘people data labs’). You must use valid PDL field names and nested subfields (e.g., `experience.title.name`, not `experience`). Only `SELECT *` is supported — column selection is not. DO NOT include a `LIMIT` clause; PDL rejects any SQL with `LIMIT` as HTTP 400 (`LIMIT is not supported inside of a SQL query`). Use the `size` input parameter (1–100) to control how many records come back. See the live schema for the complete constraint.
`payload.size`	`integer`	No	—	Maximum matched profiles to return (1-100). Each returned profile is billed separately. Start with 1 to validate the query and inspect total; request only the number of profiles you can use.
`payload.scroll_token`	`string`	No	—	Token for retrieving the next page of results.
`payload.dataset`	`string`	No	—	Optional dataset selector supported by PDL.
`payload.titlecase`	`boolean`	No	—	Normalize output text casing.
`payload.data_include`	`string`	No	—	Comma-separated fields to include, or a leading - list to exclude. This changes response fields and payload size only; it does not reduce credits, which are based on profiles returned.
`payload.pretty`	`boolean`	No	—	Pretty-print response JSON.

Output reference

People Data Labs person search result.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`array`	No	—	—
`result.data.total`	`number`	No	—	—
`result.data.scroll_token`	`string \| null`	No	—	—
`result.data.warnings`	`array`	No	—	—
`result.data.error`	`string`	No	—	—
`result.data.status`	`number`	No	—	—
`result.meta`	`record`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: per_result (per result).
Estimated Deepline credits: 1.4 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

People Data Labs: Person Search

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation