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

# Find LinkedIn Profile

> Discover a supported profile lookup and verify candidate identity before downstream enrichment.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/task-find-linkedin-profile.md)

Find a LinkedIn profile candidate, then verify that it identifies the intended
person. This task ends with an accepted URL or a documented unresolved match.

## Before you start

Keep the person's known name, company, domain, email, and location where
available. Distinguish known evidence from guesses. More candidates do not
necessarily mean stronger identity evidence.

## 1. Discover a route for the inputs you have

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "person name company LinkedIn profile URL" --type tools,prebuilts --json
```

Inspect a returned identifier with `deepline describe <returned-id> --json`.
Read its required inputs and result shape. Do not infer a fixed Google,
Apollo, or scraper chain from the requested outcome.

For reverse lookup, search with the actual input type, such as an email.
Inspect the corresponding contract before running it.

## 2. Ask for one bounded candidate review

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Find the LinkedIn profile for this known person and company.
Inspect the current lookup contract first. Keep candidate URLs with supporting
company, title, and location evidence. Return unresolved when identity conflicts.
Do not enrich contact details or write to a CRM yet.
```

Supply the known identity separately. If custom code is needed, check that
Play before running the pilot. Use the [authoring guide](https://deepline.com/docs/sdk-v2/plays.md).

## 3. Evaluate the candidate

Compare the returned person and company evidence with the supplied identity.
A matching name alone is insufficient for a common-name case. Name variants
expand the search. they do not verify a person.

Preserve conflicting candidates for review. Do not turn the first search
result into a confirmed profile without the required evidence.

> [!TIP]
>
> The accepted URL and supporting identity refer to the intended person.
> Otherwise, keep an unresolved result with the missing or conflicting evidence.

Only then use the URL in a [work-email lookup](https://deepline.com/docs/plays/task-find-work-email.md).
Ask your agent which evidence resolved the identity before expanding to a file.


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