Menu
Extract Clay table/workbook data to local files - use when you need a full-fidelity workbook export, a template-shaped snapshot of a table, or raw paginated row dumps for offline processing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | clay-export |
| description | Extract Clay table/workbook data to local files - use when you need a full-fidelity workbook export, a template-shaped snapshot of a table, or raw paginated row dumps for offline processing. |
Every export in this skill writes real row data (contact info, enrichment results, sometimes raw action-cell payloads) to your local disk. None of it belongs in a public repo - see the redaction rule at the bottom before you share anything you exported.
python3 scripts/full_export.py wb_TEST_WORKBOOK ./exports/wb_TEST_WORKBOOK
externalContent (the full raw payload behind an enrichment result, not just its
display value).<table>__raw.json, <table>__flat.csv,
<table>__schema.json.../.clay-session relative to the script - same
parent-directory session as everything else (/clay-onboarding).node clay-v2.js workbook-export wb_TEST_WORKBOOK --include-rows 20 --out workbook.json --template-out table.yaml
--template-out file additionally writes a spec-shaped YAML you can feed straight
into export-spec/apply-spec (/clay-build-table) - useful when you want the
shape of a workbook without a full data dump.clay-v2.js is redacted by default; pass --raw only when you
specifically need unredacted values and understand you now own keeping that file
private.node clay-api.js table-records t_TEST_TABLE gv_TEST_VIEW
node clay-api.js rows t_TEST_TABLE gv_TEST_VIEW 50 0
rows <tableId> <viewId> [limit] [offset] - manual pagination, no redaction layer.table-records returns the view's records directly. Neither command redacts output
.csv, .xlsx, .har, screenshots, and similar file types are structurally
disallowed anywhere in this repo - the CI safety scanner (scripts/scan-repo.js)
blocks them outright, and for good reason: a table export is contact data.runs//exports/ directories (or entirely
outside the repo) - never git add an export.node clay-v2.js redact export.json --report redact-report.json first (see /clay-run-enrichment), or hand-pick a couple of rows
and manually replace names/emails/domains with placeholders like {{email}}./clay-security-guide for the full list of what actually leaks and how the
scanner catches it.Set up auth, session, and profile config for clay-cli before running any command - use when a Clay command fails with "session expired", when starting fresh in a new checkout, or when configuring workspace/folder/workbook IDs for the first time.
Discover Clay actions and manage the local action catalog - use when searching for an available action/integration, checking catalog coverage against the strict proof registry, classifying action safety, or generating action templates.
Run a full Clay playbook end to end - intake, plan, prepare, sample, verify, scale - use when a plain-language request should be routed to one of the 12 packaged playbooks and operated through to a safe scale decision, not just a single ad-hoc command.
Build Clay list-building sources - company-to-people waterfalls, source preview/import, and webhook intake - use when adding a new list-building source to a table or converting a companies table into a people search.
Build and modify Clay tables, views, fields, and records with clay-v2.js - use when creating a new table/workbook, adding or editing columns (text/formula/http-api/use-ai/action), managing views, or writing declarative table specs.
Read-only exploration of Clay tables, workbooks, sources, and workspace metadata - use when you need to understand a table's shape, check run status, list workspaces/tables, or pull credit usage without changing anything.