Optimize Clay API performance with caching, batching, and connection pooling.
Use when experiencing slow API responses, implementing caching strategies,
or optimizing request throughput for Clay integrations.
Trigger with phrases like "clay performance", "optimize clay",
"clay latency", "clay caching", "clay slow", "clay batch".
Optimize Clay table processing speed, enrichment hit rates, and credit efficiency. Clay processes enrichment columns sequentially per row, and each enrichment column makes external API calls. Performance tuning focuses on reducing wasted enrichments, ordering columns optimally, and managing table auto-run behavior.
Prerequisites
Clay table with enrichment columns configured
Understanding of which providers are in your waterfall
Access to Clay table settings and column configuration
Instructions
Step 1: Order Enrichment Columns by Speed
Clay runs enrichment columns left-to-right. Place fast columns first:
Column Type
Typical Speed
Position
Company lookup (Clearbit)
~100ms
First (fastest)
Email finder (single provider)
~200ms
Second
Email waterfall (multi-provider)
1-10s
Middle
Claygent AI research
5-30s
Later
HTTP API (outbound call)
Variable
Last
AI text generation
2-5s
After Claygent
Why order matters: Fast columns populate data that slow columns may need as input (e.g., company name feeds into Claygent research prompt).
Step 2: Add Conditional Run Rules
Prevent enrichments from running on rows that won't yield results:
# In Clay column settings > "Only run if" condition:
# Email waterfall: only run if we have enough input data
ISNOTEMPTY(domain) AND ISNOTEMPTY(first_name) AND ISNOTEMPTY(last_name)
# Claygent: only run for high-value prospects
ICP Score >= 60 AND ISNOTEMPTY(Company Name)
# CRM push: only run for enriched, qualified leads
ICP Score >= 70 AND ISNOTEMPTY(Work Email)
This prevents:
Waterfall enrichment on rows with missing domains (wasted credits)
Claygent research on low-value prospects (expensive AI credits)
Rule of thumb: Apollo + one backup provider covers 80-85% of findable work emails. Adding more providers gives diminishing returns.
Step 5: Use Table-Level Auto-Update Controls
# Table Settings in Clay UI:
table_auto_update: ON # Parent switch: if OFF, nothing auto-runs
column_settings:
company_lookup:
auto_run: ON # Runs on every new row
email_waterfall:
auto_run: ON # Runs on every new row (if condition met)
condition: "ISNOTEMPTY(domain)"
claygent_research:
auto_run: OFF # Manual trigger only (expensive)
crm_push:
auto_run: ON # Auto-push qualified leads
condition: "ICP Score >= 70"
Step 6: Schedule Large Imports for Off-Peak
Clay's enrichment providers respond faster during off-peak hours (US nighttime):
