Diagnose and fix the most common Clay errors and integration issues.

MITAuto-check passedBackend & APIs

Install Clay Common Errors

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-common-errors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-common-errors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clay-common-errors .claude/skills/clay-common-errors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clay-common-errors
GitHub stars
2.8k
Token cost
~2k tokens
SKILL.md length
782 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Diagnose and fix the most common Clay errors and integration issues.

  • Works in 3 steps: Click the errored cell to see the full… → Test the API call independently with curl → Verify the response JSON path selector…
  • Encountering Clay errors
  • SKILL.md covers Overview, Prerequisites, Instructions and Error Handling, plus 4 more sections
  • Calls curl and jq

What it does

Clay Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Diagnose and fix the most common Clay errors and integration issues. Use when encountering Clay errors, debugging failed enrichments, or troubleshooting webhook delivery problems. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay", "clay enrichment failed", "clay webhook error".

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering Webhooks and Debugging. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Encountering Clay errors
  • Debugging failed enrichments
  • Troubleshooting webhook delivery problems
  • With phrases like clay error

Example prompts

  • “clay error”
  • “fix clay”
  • “clay not working”
  • “/clay-common-errors”

Requirements

  • A credential in YOUR_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Grep, Bash(curl:*)

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Click the errored cell to see the full error response
  2. Test the API call independently with curl
  3. Verify the response JSON path selector matches the actual response structure

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • university.clay.com
    • community.clay.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Clay Common Errors loads about 2k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 782 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 782 words, ~2,005 tokens.

Download SKILL.mdSave it as .claude/skills/clay-common-errors/SKILL.md (or your agent's skills folder).
name
clay-common-errors
description
Diagnose and fix the most common Clay errors and integration issues. Use when encountering Clay errors, debugging failed enrichments, or troubleshooting webhook delivery problems. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay", "clay enrichment failed", "clay webhook error".
allowed-tools
Read, Grep, Bash(curl:*)
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, clay, debugging

Clay Common Errors

Overview

Quick reference for the top 12 most common Clay errors across webhooks, enrichment columns, HTTP API columns, Claygent, and CRM integrations. Each error includes the exact symptom, root cause, and fix.

Prerequisites

  • Clay account with an active table
  • Access to Clay table error indicators (red cells, exclamation marks)
  • Browser developer tools for webhook debugging

Instructions

Error 1: Webhook Returns 422 Unprocessable Entity

Symptom: Data sent to webhook URL but rows never appear in table.

Cause: Invalid JSON payload or missing Content-Type header.

Fix:

bash
# Always include Content-Type header
curl -X POST "$CLAY_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"email": "test@example.com", "domain": "example.com"}'

# Validate JSON before sending
echo '{"email": "test@example.com"}' | jq . || echo "Invalid JSON!"

Error 2: Webhook URL Returns 404

Symptom: 404 Not Found when POSTing to webhook URL.

Cause: Table was deleted, webhook was replaced, or URL was copied incorrectly.

Fix: Open the Clay table, click + Add > Webhooks > Monitor webhook, and re-copy the URL. Each table has a unique webhook ID.


Error 3: Enrichment Column Shows "No Data Found"

Symptom: Enrichment column returns empty for most rows.

Cause: Input data quality is poor (personal email domains, invalid domains, missing fields).

Fix:

typescript
// Pre-validate before sending to Clay
const personalDomains = ['gmail.com', 'yahoo.com', 'hotmail.com', 'outlook.com', 'icloud.com'];

function isEnrichable(row: { domain?: string; email?: string }): boolean {
  if (!row.domain || !row.domain.includes('.')) return false;
  if (personalDomains.some(d => row.domain!.endsWith(d))) return false;
  if (row.email && personalDomains.some(d => row.email!.endsWith(d))) return false;
  return true;
}

Error 4: "Credit Balance Insufficient"

Symptom: Enrichment stops mid-table with credit error.

Cause: Monthly credit allowance exhausted.

Fix: Check credit balance in Settings > Plans & Billing. Options:

  • Connect your own provider API keys (saves 70-80% credits)
  • Reduce waterfall depth (fewer providers = fewer credits per row)
  • Upgrade plan for more monthly credits

Error 5: Webhook Submission Limit Reached (50K)

Symptom: Webhook stops accepting new submissions silently.

Cause: Each webhook source has a hard limit of 50,000 submissions.

Fix: Create a new webhook source on the same table. The 50K limit persists even after deleting rows -- you must create a fresh webhook.


Error 6: HTTP API Column Returns Error

Symptom: Red error indicator on HTTP API enrichment column cells.

Cause: Target API URL is wrong, auth header is incorrect, or response format unexpected.

Fix:

  1. Click the errored cell to see the full error response
  2. Test the API call independently with curl:
bash
curl -X POST "https://api.example.com/endpoint" \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"test": "data"}'
  1. Verify the response JSON path selector matches the actual response structure

Error 7: Claygent Returns "Could Not Find Information"

Symptom: Claygent column returns empty or generic responses.

Cause: Prompt is too vague, company is too small/private, or website blocks bots.

Fix:

  • Make prompts specific: "Find the CEO's name from the About page at {{domain}}" vs "Research this company"
  • Add fallback instructions: "If the information is not on the website, check LinkedIn and Crunchbase"
  • Use Navigator mode for JavaScript-heavy sites

Error 8: Enrichment Runs on Existing Rows Unexpectedly

Symptom: Credits consumed on rows that were already enriched.

Cause: Table-level auto-update is ON and a column was edited, triggering re-enrichment.

Fix: Go to Table Settings and toggle auto-update OFF at the table level. Then enable auto-run only on specific columns that need it. The table-level setting is the parent: if OFF, no columns auto-run.


Show full SKILL.md (324 more words)Show less
Error 9: Rate Limited (429) on Webhook Submissions

Symptom: 429 Too Many Requests when sending data via webhook.

Cause: Explorer plan has a 400 records/hour throttle.

Fix:

typescript
// Add delay between webhook submissions
async function sendWithThrottle(rows: any[], webhookUrl: string) {
  for (const row of rows) {
    const res = await fetch(webhookUrl, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(row),
    });
    if (res.status === 429) {
      const retryAfter = parseInt(res.headers.get('Retry-After') || '60');
      console.log(`Rate limited. Waiting ${retryAfter}s...`);
      await new Promise(r => setTimeout(r, retryAfter * 1000));
    }
    await new Promise(r => setTimeout(r, 250)); // 250ms between requests
  }
}

Error 10: CRM Sync Creates Duplicate Contacts

Symptom: Same contact appears multiple times in HubSpot/Salesforce.

Cause: No deduplication key configured in the CRM push action.

Fix: When configuring the CRM action column, use email as the unique identifier and select Update existing record if found rather than always creating new.


Error 11: CSV Import Column Mapping Wrong

Symptom: Data appears in wrong columns after CSV import.

Cause: CSV headers don't match Clay column names exactly.

Fix: Normalize headers before import: trim whitespace, match case exactly. "Company Name" and "company_name" are treated as different columns.


Error 12: Formula Column Shows Error

Symptom: Formula column displays #ERROR or #REF.

Cause: Column name referenced in formula was renamed or deleted.

Fix: Edit the formula column and update all column references to match current names. Clay formulas reference columns by their display name (case-sensitive).

Error Handling

SymptomQuick CheckLikely Fix
Red cell indicatorClick cell for error detailFix API config or input data
Empty enrichmentCheck provider connectionReconnect in Settings > Connections
No new rows from webhookTest webhook URL with curlRe-create webhook source
Credits depleting fastCheck waterfall depthReduce to 2 providers, add conditions

Output

Produce a redacted diagnostic record with table/environment, observed symptom, correlation ID, likely cause, containment action, data-certification state, and named escalation owner. Avoid including raw contacts, CRM records, credentials, or complete provider responses in tickets and shared logs.

Examples

When CRM sync duplicates a contact, pause the affected action, verify the deduplication key with a synthetic row, and repair/update the existing record before resuming. When credits drain unexpectedly, disable auto-runs, preserve the table state, and review conditions and waterfall behavior before retrying.

Resources

Next Steps

For systematic debugging, see clay-debug-bundle.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.curated/clay-common-errors of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Clay Common Errors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clay Common Errors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clay Common Errors this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Tg Bot Opsserejaris/personal-corp-os229—~1.6kAutomated safety check: NotesMIT
Make Scenario Operationsintegromat/make-skills128—~1.2kAutomated safety check: PassMIT
Shopify DebuggingMicrock/ordinary-claude-skills404—~3.8kAutomated safety check: PassCustom licence
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Novu Design Workflownovuhq/novu40k—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • Tg Bot Ops

    serejaris/personal-corp-os

    A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.

    229 GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Make Scenario Operations

    integromat/make-skills

    A skill your agent uses when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing.

    128 GitHub stars~1.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Shopify Debugging

    Microck/ordinary-claude-skills

    Complete debugging and troubleshooting guide for Shopify including Liquid errors, theme preview debugging, API error handling, JavaScript console debugging, network request inspection, cart issues…

    404 GitHub stars~3.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.

    40k GitHub stars~2.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • MQTTX CLI

    emqx/MQTTX

    Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.

    5.1k GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Clay Common Errors

What does Clay Common Errors do?

Diagnose and fix the most common Clay errors and integration issues. Clay Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Diagnose and fix the most common Clay errors and integration issues.

When should I use Clay Common Errors?

Clay Common Errors fits situations like: encountering Clay errors; debugging failed enrichments; troubleshooting webhook delivery problems; with phrases like clay error.

How do I install Clay Common Errors in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-common-errors -a claude-code`. Or copy the skill folder (skills/.curated/clay-common-errors in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clay-common-errors in your project. Claude Code loads it when a task matches its description.

How do I install Clay Common Errors in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-common-errors -a codex`. Or copy the skill folder (skills/.curated/clay-common-errors in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clay-common-errors in your project. Codex loads it when a task matches its description.

Can I use Clay Common Errors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-common-errors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clay-common-errors, .gemini/skills/clay-common-errors, .github/skills/clay-common-errors and .opencode/skills/clay-common-errors in your project.

What does Clay Common Errors need to run?

Going by SKILL.md and its folder, Clay Common Errors needs the command-line tools its instructions call (curl and jq). Our summary lists: A credential in YOUR_KEY. Its frontmatter pre-approves these tools: Read, Grep, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Clay Common Errors access the network?

SKILL.md names 2 domains. As links in the text: university.clay.com and community.clay.com. This is read from the text; nothing was executed.

Is Clay Common Errors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clay Common Errors use?

Clay Common Errors is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clay Common Errors use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clay Common Errors?

Skills that share tags, products or a category with Clay Common Errors: Tg Bot Ops (serejaris/personal-corp-os, 229 stars), Make Scenario Operations (integromat/make-skills, 128 stars), Shopify Debugging (Microck/ordinary-claude-skills, 404 stars) and Supabase Development and Debugging (supabase/agent-skills, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clay Common Errors?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.