/deepline-gtm

name: deepline-gtm
description: "GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,buyercaddy,cbinsights,clay,clickhouse,close,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,deepseek,discolike,dnb,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,kickbox,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meerapi,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,particle,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,…."

Deepline GTM

Deepline is a GTM tool routing and automation platform for any ad-hoc or automated GTM task, with thousands of tools for prospecting, enrichment, research, agentic work, and more.

First

Start with a task to complete. Run

deepline billing balance && deepline search "<input you have -> result you need>"

to get the current balance and the relevant tools with their prices. If `deepline` is not found, install it by following https://code.deepline.com/INSTALL.md. If search fails, follow the printed instructions.

For a multi-step task, identify the first capability you need and search for it. Search matches your words against what each tool takes and returns. Describing the data, like "<what you have> -> <the final result you need>", works better than naming a method or a middle step, and rephrasing the query often turns up different tools. `deepline search --help` has examples.

Search and help are how you learn Deepline. Search finds what to run; `deepline <command> --help` explains how to run it: its purpose, inputs, outputs and cost, with `--verbose` for field-level detail. Read a command's help before you first use it. `deepline --help` lists every command.

When search returns a relevant doc, read it with `deepline describe <doc id>` before you start: docs have steps you haven't thought of or may miss.

Final message: read before you reply

Reply in this shape and nothing else:

## Deepline Results

- **<Outcome, key count in bold>.**
- <What is missing, as counts by reason, e.g. "1 not found, 1 unconfirmed".>
- **[View the run in your browser](<runUrl>)** · [Get the CSV](<path>)
- Spend: <N> Deepline credits.

| <columns the user asked for> |
| --- |
| <rows> |

**Next:** <one sentence>

1. Say each fact once. The outcome is the first bullet; do not restate it. 2. Bullets: the outcome, what is missing, links, and spend, each one line of about 15 words. Report misses as counts by reason; the table shows which rows, so never name rows in a bullet. Add one more bullet only for a caveat that changes what the user should do. Leave out how you worked and why a lookup failed. 3. Links start with the action. Put the run link first, in bold: **View the run in your browser**, linked to its run page: the play page with `?runId=<URL-encoded run ID>` (`runUrl`). If the printed page or `dashboardUrl` lacks `?runId=`, add it. Then the files: "Get the CSV". Save files you link in the user's working directory, never a temp directory such as `/tmp`, which gets cleaned up. With several runs, say what each did: "View the email lookup run in your browser." Link only files and pages that exist. 4. Table: the rows the user asked for (a labeled sample if large), their inputs and the outputs they asked for, short cells. When results differ in confidence, add a Status column (validated, unconfirmed, not found). 5. Next: the most useful continuation. For repeatable work, offer to run it on Deepline on a schedule. 6. This is your last message: stop any background watchers before you send it.

1. Choose what to run

For failing, stuck, partial, or incorrect Play runs, use `deepline-triage` alongside this skill. It also discovers failures when no Play is named.

**Decide the task's shape first.**

• **Find everything** (a complete list: every company that matches, everything

a source holds about an account): completeness matters most. It usually pays to cast a wide net: try a few different searches and complementary sources, and merge what you find.

• **Fill in fields for given rows** (one value per row: an email per person, a

domain per company): coverage matters. After a first pass, it's usually worth a different search or source for the rows that are still empty before you wrap up.

• **Company criteria drive the task:** find the companies first, then the

people there.

Either way, save the first pass as the deliverable before trying more, keep it current as later passes finish, and leave time to deliver.

Then choose what to run:

• **Tool:** one operation, such as looking up a profile or validating an email.

Use direct tool calls for isolated spot checks.

• **Play:** TypeScript that expresses GTM work as code. It combines tools with

custom logic and processes batches. Deepline handles provider rate limits and retries, persists progress and results, and supports recovery after failures.

• **A tool or prebuilt Play covers the task:** use it directly.
• **Prefer sources that return evidence** for each answer, such as a source URL

or a verified status, over lists without it. Report unverified results, such as catch-all emails, apart from verified ones.

• **A workflow or batch:** use a supplied Play, reuse or adapt a suitable

prebuilt, or author one when none fits. Do not process a batch by looping direct tool calls.

• **A CSV:** run the batch form