Choose a Deepline workflow

Use this guide when you know your starting data and your desired result, but not which Play to use. Pick one outcome, inspect the matching Play, then pilot it on a small, representative input.

Before you choose

Have these three things ready:

The data you can start from, such as a CSV with names and domains, a list of account domains, or a visitor event.
One outcome, such as a verified work email, a researched account, or a reviewed ads audience.
A small representative sample. Do not use a full list to discover whether a workflow fits.

Match your input to the job

You have	You need	Start here
First name, last name, and company domain	Verified work emails	Find work emails with a waterfall
A LinkedIn profile URL	A work email	LinkedIn to email
A known email address	Validation status	Email validation
Company name or domain	Company data	Enrich a company
Company domains and target roles	Contacts at those companies	Example prebuilt Plays
Names, companies, or emails	LinkedIn profiles, phone numbers, or company data	Example prebuilt Plays
Account domains	Evidence-backed account research before outreach	Research accounts before outreach
A visitor event from Warmly	A human-reviewed warm outbound action	Warm outbound automation
A consented first-party list	A reviewed Google Ads, Meta, or LinkedIn audience	Build a paid ads audience
An existing Clay table	One custom, versioned Play	Migrate one Clay table to a Play

Inspect a candidate without running it

Use search to find a maintained Play, then read its input contract. These commands do not start a run or spend Deepline credits.

deepline plays search "verified work email" --json
deepline plays describe prebuilt/name-and-domain-to-email-waterfall-batch --json
deepline plays check prebuilt/name-and-domain-to-email-waterfall-batch --json

plays check confirms that the current prebuilt contract is available. It does not deploy the Play or call a provider. Use a prebuilt Play for one bounded lookup with a maintained route and result rule. Use a workspace-owned Play when you need code, branching, approval logic, a trigger, or an external write. For a name-and-company lookup that should return a LinkedIn profile, start with prebuilt/person-to-linkedin-harvestapi. The same name without -harvestapi remains available for compatibility with existing saved workflows.

Continue only when the Play accepts the fields you have and returns the result you need. If either is unclear, ask your agent to explain the contract before it runs a pilot.

Ask an agent to choose when the table does not fit

Give your coding agent the file name, its column names, the outcome, and the pilot boundary:

/deepline-gtm I have leads.csv with first_name, last_name, company, and domain.
I need verified work emails. Find the applicable Play, show its input contract,
and run only a representative pilot after I approve the route.

Choosing a Play is not approval to run paid work. Keep the pilot and approval boundary explicit.

Next step

Open the guide for the job you selected. Each guide explains its prerequisites, safe validation step, pilot, and the result to review before you scale.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Choose a Deepline workflow

Before you choose

Match your input to the job

Inspect a candidate without running it

Ask an agent to choose when the table does not fit

Next step

​Before you choose

​Match your input to the job

​Inspect a candidate without running it

​Ask an agent to choose when the table does not fit

​Next step

Before you choose

Match your input to the job

Inspect a candidate without running it

Ask an agent to choose when the table does not fit

Next step