Limadata: Find Person Profiles

Find a known person’s LinkedIn, GitHub, and X profile URLs from name plus company, company domain, or work email.

Tool ID: limadata_find_person_profiles

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(
  'limadata_find_person_profiles',
  {
    "full_name": "Example"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute limadata_find_person_profiles --input '{
  "full_name": "Example"
}' --json

Example response

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

{
  "data": {
    "linkedin_url": "https://www.linkedin.com/in/jane-doe",
    "github_url": "https://example.com",
    "x_url": "https://example.com"
  }
}

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

Input reference

Find a person’s social profile URLs, like LinkedIn, by searching across multiple data sources using their full name combined with additional identifying information. #### Required Parameters - Person’s Name: The person’s name is required. You can send partial name like Bill G as well. - At least one of the following: - Company Name (current or past employer) - Company Domain (e.g., microsoft.com) - Email Address (work email only) #### Search Strategy When providing multiple parameters, our search algorithm uses all available data points to increase match accuracy: - The full name uses fuzzy matching to find the best possible match - Company name and domain help narrow down results significantly - Email is checked against our database and partner networks - Work emails only. For personal emails lookup, use the reverse email lookup endpoint #### Use Cases This endpoint is ideal See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.full_name`	`string`	Yes	—	Person’s full name. Example: William Gates Minimum length: 1.
`payload.company_name`	`string`	No	—	Company name. Example: Microsoft
`payload.company_domain`	`string`	No	—	Company domain. Optional, but helps increase resolution. Example: microsoft.com
`payload.email`	`string`	No	—	Person’s Business Email. Example: wjones@microsoft.com

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.linkedin_url`	`string \| null`	No	—	—
`result.data.github_url`	`string \| null`	No	—	—
`result.data.x_url`	`string \| null`	No	—	—
`result.data.facebook_url`	`string \| null`	No	—	—
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0.56 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Limadata: Find Person Profiles

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