Skip to main content
Clay tables are column-based — each column is a separately configured enrichment or AI step. Deepline is outcome-centric: describe what you’re trying to achieve and Claude selects the right tools to get there.
The video walks through a real Clay table with email waterfalls, Claygent research, and ICP scoring — the full flow from table → phase 1 doc → scripts → output CSV.

What you need

A Clay table

The table you want to migrate.

Claude Code

Install from claude.ai/code and log in.

Deepline CLI

Runs the enrichment scripts Claude Code generates. Install below.
You can use this skill just to document a Clay table without running anything. If that’s your goal, skip to Documentation-Only Path at the bottom.

Install Deepline

Deepline is what runs the enrichment. It wraps providers like LeadMagic, Exa, Instantly, and Claude into a single command. Ask your coding agent to set it up:
If you prefer the terminal:
Setup verifies the CLI, skills, authentication, and workspace before it finishes. Use deepline doctor --json if setup reports a problem.
You don’t need Deepline if you just want a Phase 1 doc (table summary + dependency graph + pass plan). You only need it when you want to actually run the output scripts.

The workflow

Four steps. The first two are in Claude Code. The last two are in your terminal.

Easy path: the Clay Extract bookmarklet

Instead of capturing network logs by hand, use the Clay Extract bookmarklet. It runs in your already-logged-in Clay tab, pulls the full table config, schema, sample records, and all cell data, then downloads a single clay_extract_<table>.json you can hand straight to /clay-to-deepline. Your session cookie is never read or stored, only your browser uses it.
1

Add the bookmarklet

Drag the purple button above to your bookmarks bar. Or click it to copy the code, create a new bookmark, and paste it as the URL.
2

Open your Clay table

Go to the table view you want, e.g. app.clay.com/workspaces/.../tables/t_xxx/views/gv_xxx.
3

Click the bookmarklet

A progress toast appears bottom-right, then clay_extract_<table>.json downloads automatically.
4

Hand it to Claude Code

Run /clay-to-deepline and attach the downloaded JSON. No cURL, no DevTools.
This is exactly what runs. It only calls api.clay.com v3 read endpoints with your existing browser session and downloads the result locally. Nothing is sent anywhere else.
Prefer doing it by hand, or the bookmarklet didn’t work? The manual network-log path still works, step by step below.

Step 1 — Capture your Clay table’s network logs

  1. Open app.clay.com in Chrome and log in
  2. Open DevTools: Cmd+Option+I on Mac, or F12 on Windows
  3. Click the Network tab
  4. Reload the page (or click around in your Clay table to trigger requests)
  5. In the filter box, type api.clay.com to show only Clay API calls
  6. Click any request in the list
  7. Right-click → CopyCopy as cURL
On Mac it’s “Copy as cURL (bash)”. On Windows it’s “Copy as cURL (cmd)” — either works, the skill strips what it needs.
The copied command will look like:
The part you need is everything between the -b '...' quotes — that’s your session cookie.

Step 2 — Run /clay-to-deepline in Claude Code

Open Claude Code and type:
Then give it your Clay table. You can paste:
  • A Clay table URL (e.g. app.clay.com/workbooks/xxx/tables/yyy)
  • A JSON export from the table
  • Network logs or HAR file captured from Chrome DevTools
Network logs contain session cookies. The cookies are not shared with Deepline, but don’t share them externally.
Claude Code reads the table structure and the actual AI prompt templates embedded in each column. The richer your input, the more accurate the output. Review the Phase 1 doc — Claude Code produces three things before writing any scripts:
  • Table summary — every column, what Clay action it runs, what model, what the output looks like
  • Dependency graph — which columns feed into which (execution order at a glance)
  • Pass plan — the ordered list of Deepline tool calls that replicate each Clay action
Check that:
  • Prompt templates are recovered verbatim (approximated ones are flagged with ⚠️)
  • The pass plan matches what your table actually does
  • ICP scoring criteria are correct (the skill can’t invent these)
Once you’re happy, say “looks good” and Claude Code writes the scripts.

Step 3 — Run the scripts

Claude Code generates two scripts in a scripts/ folder:
Start with a pilot run (3 rows) before doing the full table:
For paid tools (Exa, LeadMagic, email waterfalls), the skill adds a pilot gate automatically. You’ll see a preview before any money is spent.

Step 4 — Get your output

Run the normalizer to produce clean CSVs:
You get:
  • output/contacts.csv — every person with enriched fields (email, job function, AI-generated research, ICP score)
  • output/accounts.csv — every company with verified name, domain, social links, HQ address, CEO
Or push directly to a campaign:

What you get

The migration produces a self-contained project folder:
The scripts are plain bash. You can read them, edit them, schedule them with cron, or run them in CI.

How Clay actions map to Deepline

The skill handles these automatically — this is just so you know what’s happening:

Accuracy

26-row production test against Clay ground truth (March 2026). Small sample size — results are directional, not statistically definitive: The ~15% research gap is mostly name collisions — e.g. onit.com resolving to NASDAQ:ONIT instead of the legal-ops software company.
The skill’s “confidence” label on research rows doesn’t mean what you’d expect. “Low” confidence often has great content — it just means the LLM found blog posts instead of 10-K filings. Judge by whether the content is specific to the company, not by the confidence score.

Cost comparison

Same 26-row test (March 2026). Clay cost uses Argon model (3 data credits/row for 10-step research). Credit prices from Clay pricing. Content quality is equivalent. For large public companies, Deepline can be more current - Exa indexes recent blog and PR content faster than Google indexes 10-Ks.

Documentation-only path

If you just want to document a Clay table — understand what it does, map its dependencies, build a reference for the team — you don’t need to run anything.
  1. Install ClayMate Lite from GitHub
  2. Open your Clay table in Chrome
  3. Click the extension icon → “Export JSON”
  4. Drag the downloaded *.json file into Claude Code
  5. Run /clay-to-deepline and ask for Phase 1 docs only
You’ll get a full table summary, dependency graph, and pass plan — without running a single script or spending anything.
ClayMate Lite exports include the table schema + sample rows. This is the richest input short of a full HAR file. For most tables it’s enough to recover the actual AI prompt templates from cell values.

Feedback or issues?