> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Limadata: Find Person Profiles

> Find a known person's LinkedIn, GitHub, and X profile URLs from name plus company, company domain, or work email. Includes SDK V2 examples, schemas, and cost.

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

> [!NOTE]
>
> Tool ID: `limadata_find_person_profiles`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
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

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute limadata_find_person_profiles --input '{
  "full_name": "Example"
}' --json
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "linkedin_url": "https://www.linkedin.com/in/jane-doe",
    "github_url": "https://example.com",
    "x_url": "https://example.com"
  }
}
```

Use `deepline describe 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](mailto:wjones@microsoft.com) |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "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 for individual profile lookups in applications like CRM enrichment, contact verification, or lead validation #### Rate limit This endpoint is exempt from the global rate limit and can support higher concurrency. - Charged on each call, including 404s.",
    "properties": {
      "full_name": {
        "type": "string",
        "description": "Person's full name. Example: William Gates",
        "minLength": 1
      },
      "company_name": {
        "type": [
          "string",
          "null"
        ],
        "description": "Company name. Example: Microsoft"
      },
      "company_domain": {
        "type": [
          "string",
          "null"
        ],
        "description": "Company domain. Optional, but helps increase resolution. Example: microsoft.com"
      },
      "email": {
        "type": [
          "string",
          "null"
        ],
        "description": "Person's Business Email. Example: wjones@microsoft.com"
      }
    },
    "required": [
      "full_name"
    ],
    "additionalProperties": false
  }
  ```
</details>

## 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). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "linkedin_url": {
            "type": [
              "string",
              "null"
            ]
          },
          "github_url": {
            "type": [
              "string",
              "null"
            ]
          },
          "x_url": {
            "type": [
              "string",
              "null"
            ]
          },
          "facebook_url": {
            "type": [
              "string",
              "null"
            ]
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

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

## Related documentation

* [Limadata provider guide](https://deepline.com/docs/providers/limadata/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.