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".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
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:*)
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","clay","debugging"]
compatibility
Designed for Claude Code, also compatible with Codex and OpenClaw
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:
# 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 sendingecho'{"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:
// Pre-validate before sending to Clayconst personalDomains = ['gmail.com', 'yahoo.com', 'hotmail.com', 'outlook.com', 'icloud.com'];
function (): {
(!row. || !row..()) ;
(personalDomains.( row.!.(d))) ;
(row. && personalDomains.( row.!.(d))) ;
;
}
isEnrichable
row: { domain?: string; email?: string }
boolean
if
domain
domain
includes
'.'
return
false
if
some
d =>
domain
endsWith
return
false
if
email
some
d =>
email
endsWith
return
false
return
true
Error 4: "Credit Balance Insufficient"
Symptom: Enrichment stops mid-table with credit error.
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.
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.
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).