Clay Table CLI

What it does

Lets you create Clay tables and add formula, AI, enrichment, or HTTP columns, and load or export rows from your own Clay account. Any column that spends credits only runs after you explicitly approve it, and every write stays contained inside the folder you choose.

When to use it

• When you use Clay to enrich prospect lists or customer data.
• When you need to create or modify Clay tables from an automated flow.
• When you want to control enrichment credit spend column by column.

Steps

1. Tell it which Clay table you want to create or modify.
2. The assistant builds the column structure (formula, AI, enrichment, HTTP).
3. It shows which columns will spend credits before running them.
4. You explicitly approve which columns run.
5. The resulting rows are loaded or exported.
6. Every change stays limited to the Clay folder you defined.

The skill

---
name: clay-table-cli
description: Builds Clay tables from your coding agent: formula, AI, enrichment, and HTTP columns, running only after your approval.
---

# Clay Table CLI

## 1. What it does

- Lets you create Clay tables and add formula, AI, enrichment, or HTTP columns, and load or export rows from your own Clay account. Any column that spends credits only runs after you explicitly approve it, and every write stays contained inside the folder you choose.

## 2. When to use it

- When you use Clay to enrich prospect lists or customer data.
- When you need to create or modify Clay tables from an automated flow.
- When you want to control enrichment credit spend column by column.

## 3. Step by step

- Tell it which Clay table you want to create or modify.
- The assistant builds the column structure (formula, AI, enrichment, HTTP).
- It shows which columns will spend credits before running them.
- You explicitly approve which columns run.
- The resulting rows are loaded or exported.
- Every change stays limited to the Clay folder you defined.

## 4. Safety rules

- Safety rules: everything ships as a draft first; nothing is sent, published, or paid for without your explicit approval; no data, numbers, or results are ever invented; no credentials or secrets are typed into chat.

## 5. Best practices

- Always review the full draft before approving any send, publish, or payment.
- If real information (data, numbers, results) is missing, ask for it to be flagged as pending instead of invented.
- Keep credentials and keys out of chat; set them in environment variables or your secrets manager.

## 6. GoHighLevel integration

- Where relevant, results can be saved as contacts, tags, tasks, or notes inside your GoHighLevel sub-account.
- No automation inside GHL (workflow, campaign, trigger) activates without your review first.

For Claude Code, save it as ~/.claude/skills/clay-table-cli/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.