Skip to main content
This tutorial gives you one observable success: a completed Play run whose result you can inspect. It uses a Deepline-maintained Play, so you do not need to write or publish code first.

​
Before you start

You need the Deepline CLI installed from the main Quick Start, plus an approved workspace.

​
1. Confirm you are authenticated

You should see connected: true and the workspace you are using. If it reports that you are not connected, run deepline setup --json — it installs skills, connects this machine, and verifies the result in one command.

​
2. Inspect the Play

Before running anything, ask Deepline what the Play expects:
Look for required inputs and example output. If you are using Claude Code, ask it to summarize the schema in plain English.

​
3. Pilot one real record

Use a real lead you are allowed to enrich. Placeholder people may return no result.
Good outcome: the run finishes and returns verified contact data or a clear no-result reason.

​
4. Pilot a CSV

Once one record looks right, use the maintained batch Play. Your leads.csv needs a linkedin_url column. Keep the first pilot to a few real records you are allowed to enrich. Validate its contract without deploying or spending credits:
Then create a small pilot file and run it:
Use the run ID printed by the command to export the completed rows:
A useful pilot finishes with a completed run and exported rows. Each row contains an email result or a clear no-result reason. Review those rows before you run the full file.

​
5. Write a custom Play when the standard path no longer fits

Write code when your process needs business logic, such as:
  • search once a week and send new matches to Salesforce
  • run a different enrichment path for VPs vs directors
  • try providers in your preferred waterfall order
  • score accounts and export a chart
Use Write Workflows for the authoring model and Examples for complete starting points. Check a local Play before you run it:
This validates the Play without starting a run or spending credits.

​
Ask Claude Code

Use plays check whenever Claude Code writes or edits a play. It catches SDK syntax and play-shape problems before money or time gets spent.