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

# Example Prebuilt Plays

> Choose and run a maintained prebuilt Play for one bounded lookup, then review a pilot before you use it on a full list.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/tasks-overview.md)

> [!NOTE]
>
> Choose one maintained lookup whose required identifiers and output fit the
> job.

A **prebuilt Play** is a Deepline-maintained operation with a defined input,
result rule, and run record. Use one for a bounded lookup, such as a work email,
LinkedIn profile, mobile phone number, company profile, or set of contacts at an
account. Use a custom [Play](https://deepline.com/docs/plays/plays-overview.md) when the job needs your own
code, a trigger, several steps, approval logic, or an external write.

## Choose a starting Play

| You need | Start here |
| - | - |
| Work email from a name and domain | [Find work emails with a waterfall](https://deepline.com/docs/plays/email-waterfall.md) |
| Work email from a LinkedIn URL | [Find work email](https://deepline.com/docs/plays/task-find-work-email.md) |
| Personal email | [Find personal email](https://deepline.com/docs/plays/task-find-personal-email.md) |
| Mobile phone | [Find mobile phone](https://deepline.com/docs/plays/task-find-mobile-phone.md) |
| LinkedIn profile | [Find LinkedIn profile](https://deepline.com/docs/plays/task-find-linkedin-profile.md) |
| Contacts at a target company | [Find decision makers](https://deepline.com/docs/plays/task-find-decision-makers.md) |
| Company details | [Enrich a company](https://deepline.com/docs/plays/task-enrich-company.md) |

If you do not know the exact Play name, search the live catalog:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline search --type prebuilts "work email company phone linkedin"
```

## Validate the contract first

Read the Play's input and output contract, then validate that it is available:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe prebuilt/name-and-domain-to-email-waterfall
deepline plays check prebuilt/name-and-domain-to-email-waterfall
```

This validation does not deploy the Play, start a run, or spend Deepline
credits.

## Run one representative lookup

Use a real row whose answer you can review:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline plays run prebuilt/name-and-domain-to-email-waterfall \
  --input '{"first_name":"Jane","last_name":"Smith","domain":"example.com"}' \
  --watch
```

The run can call paid providers. Review the returned value, any no-result
reason, and the Deepline-credit usage before you use the Play on a file.

> [!TIP]
>
> A prebuilt Play can return no result. Having the expected fields does not
> guarantee coverage or delivery.

## Move to a file only after the lookup is right

For a CSV, use the matching batch Play and a separate pilot file. The [email
waterfall guide](https://deepline.com/docs/plays/email-waterfall.md) shows the complete sequence, including
safe contract validation, a representative pilot, and export.

## Next step

When one lookup is not enough, write a custom [Play](https://deepline.com/docs/plays/plays-overview.md) that
keeps your transformation, approval, and destination logic in one reviewed
workflow.

## Verify this task

Describe and check the selected Play. Confirm required row fields and source identity before a small authorized run.

Ask your agent to explain a failed check before repeating work or expanding the scope.


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