Example Prebuilt Plays

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 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
Work email from a LinkedIn URL	Find work email
Personal email	Find personal email
Mobile phone	Find mobile phone
LinkedIn profile	Find LinkedIn profile
Contacts at a target company	Find decision makers
Company details	Enrich a company

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

deepline plays search "work email company phone linkedin" --json

Validate the contract first

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

deepline plays describe prebuilt/name-and-domain-to-email-waterfall --json
deepline plays check prebuilt/name-and-domain-to-email-waterfall --json

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:

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.

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 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 that keeps your transformation, approval, and destination logic in one reviewed workflow.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Example Prebuilt Plays

Choose a starting Play

Validate the contract first

Run one representative lookup

Move to a file only after the lookup is right

Next step

​Choose a starting Play

​Validate the contract first

​Run one representative lookup

​Move to a file only after the lookup is right

​Next step

Choose a starting Play

Validate the contract first

Run one representative lookup

Move to a file only after the lookup is right

Next step