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

# Person enrichment from email

> The People Data Labs reverse-enrichment tool contract for matching a known email to a person.

Callable tool: `peopledatalabs_enrich_contact`. This page describes a direct
People Data Labs lookup, not a Deepline prebuilt waterfall.

## Input

For an email lookup, supply `email`. Other matching inputs include `phone`,
`profile`, `pdl_id`, name, company, and location context. Input fields are
optional in the schema, but a match needs usable identifying information.

| Field | Contract |
| - | - |
| `email` | An email the person uses or used. |
| `min_likelihood` | Integer 0–10. Deepline defaults to 6 when omitted. |
| `required` | Provider boolean expression over fields that a match must contain. |
| `data_include` | Comma-separated provider fields or subfields to return. |
| `include_if_matched` | This boolean requests metadata about matched inputs. |

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe peopledatalabs_enrich_contact --json
deepline tools execute peopledatalabs_enrich_contact \
  --input '{"email":"person@example.com","min_likelihood":6}' --json
```

The execute command can incur Deepline usage. The provider may return no person. A match does not guarantee a value for every requested profile field.
See the generated [Enrich contact contract](https://deepline.com/docs/providers/peopledatalabs/enrich-contact.md)
for the complete input and output schema, and the
[provider guide](https://deepline.com/docs/providers/peopledatalabs/guide.md) for connection instructions.

For enrichment workflow design, see [Lead enrichment](https://deepline.com/docs/recipes/lead-enrichment.md).


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