Skip to main content
Human guide: work with your agent →
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 when the job needs your own code, a trigger, several steps, approval logic, or an external write.

Choose a starting Play

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

Validate the contract first

Read the Play’s input and output contract, then validate that it is available:
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:
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.

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.