Skip to main content
Job: use a working GTM workflow without designing the waterfall yourself. A prebuilt play is a Deepline-maintained workflow. It is not a raw provider tool.

​
Find the right play

deepline plays search email --json
Look for:
FieldWhy it matters
nameWhat you run
originprebuilt means Deepline-maintained
inputSchemaWhat your CSV or API call must provide
runCommandCopyable CLI starter

​
Inspect it

deepline plays describe prebuilt/person-linkedin-to-email --json
Ask: “Do I have the required inputs?” not “Which provider should I call?”

​
Pilot one record

Use the same input shape everywhere: 
deepline plays run prebuilt/person-linkedin-to-email \
  --input '{"linkedin_url":"https://www.linkedin.com/in/example-person/"}' \
  --watch
If the pilot output looks right, scale through a custom play or CSV workflow.

​
Compose it inside your own play

Inside a custom workflow, call the prebuilt workflow by name only when the play compiler can statically resolve that child play in your workspace. For most users, start by running and inspecting the prebuilt directly: 
deepline plays describe prebuilt/person-linkedin-to-email --json
deepline plays run prebuilt/person-linkedin-to-email \
  --input '{"linkedin_url":"https://www.linkedin.com/in/example-person/"}' \
  --watch
Do not call prebuilt plays with deepline tools execute or ctx.tools.execute. Use deepline plays run or ctx.runPlay.