clay-common-errors

# 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 ...