Connecting Clay to n8n: setup, sync, and gotchas in 2026

How Clay and n8n Work Together

Clay accepts new rows via its REST API, and n8n calls that API on a trigger. The integration runs in one direction by default: a lead enters n8n from a webhook, HubSpot form, Typeform, or a scheduled database pull, n8n filters it, then posts it to your Clay table. Enrichment happens asynchronously inside Clay after the row lands.

That async behavior is where most setups break. The API call that adds a row returns immediately with a row ID, but the waterfall enrichment keeps running for 30 seconds to 3 minutes depending on how many providers Clay is querying. You need Clay's outbound webhook to close the loop and push results back to n8n once enrichment completes.

The full data flow: lead source pushes contact data to n8n, n8n applies ICP filters, qualifying rows post to Clay via API, Clay enriches asynchronously, Clay fires a callback webhook to n8n when done, n8n writes enriched data to your CRM or Smartlead campaign.

Step-by-Step: Setting Up the Clay + n8n Connection

This setup takes about 45 minutes the first time. You need a Clay account on Starter or higher for API access, an n8n instance (cloud or self-hosted), and API credentials for any CRM you're pushing enriched data into downstream.

1. Generate your Clay API key. In Clay, go to Settings > Integrations > API. Copy the Bearer token. It doesn't expire unless you rotate it manually.
2. Find your Clay table ID. Open the target table in Clay. The table ID appears in the URL path. Copy it.
3. Create an n8n workflow with a Webhook trigger. In n8n, create a new workflow and add a Webhook node set to POST method. Copy the generated URL. This is where your lead source will send data.
4. Add an IF node for ICP filtering. Before hitting Clay's API, add a conditional node. Filter by employee count, industry, or job title. This is the credit-saving step most teams skip entirely.
5. Add an HTTP Request node to call Clay's API. Set the URL to Clay's rows endpoint for your table (verify the exact path in Clay's current API docs). Method: POST. Authorization header: Bearer [your-api-key]. Content-Type: application/json. Map your lead fields to Clay's column names in the body. Column names are case-sensitive.
6. Configure Clay's outbound webhook for async results. In your Clay table settings, add an outbound webhook pointing to a second n8n Webhook node URL. Clay fires this after enrichment completes with all enriched fields in the payload.
7. Write enriched results downstream. In the second n8n workflow, map Clay's enriched fields to your CRM or outreach tool like Smartlead or Instantly and create or update the contact record.

Test with a single contact before activating. A 201 response confirms row creation. A 422 means your field names don't match the table column names exactly.

ICP Filtering Before Enrichment Is the Real ROI Lever

The biggest return in this integration isn't from Clay's waterfall data. It's from deciding which leads Clay never sees. Clay charges per credit regardless of whether the enriched contact converts. Running an ICP check in n8n before posting to Clay means you only enrich accounts you'd actually work.

A practical filter checks three things: employee count between 50 and 500, industry not in consumer goods or hospitality, and job title containing VP, Director, or Head of. That filter alone typically removes 35 to 55 percent of raw form submissions, per Modern Inbound data across 3,000+ enrichment workflows. At $0.15 per credit, a team processing 1,000 leads per month saves between $52 and $82 monthly. That's close to $1,000 per year on the Starter plan.

Don't over-filter. If your criteria cut 80 percent of inbound, you're probably over-indexing on a single attribute. Start with industry and company size only, then layer in job title after 30 days of data.

The Async Timing Trap That Breaks Most Clay + n8n Builds

Clay's enrichment doesn't return results in the same API call. You POST a row and get a 201 back in under 200ms, but the waterfall pull from providers like Apollo, Hunter, People Data Labs, and LinkedIn takes 30 seconds to 3 minutes depending on which providers you've enabled. If your n8n workflow tries to read enrichment data from the POST response, it reads blank fields every time.

The fix is a two-webhook architecture. Webhook 1 receives the incoming lead and posts it to Clay. Webhook 2 receives Clay's completion callback, which fires when the waterfall finishes. Your CRM write happens in Webhook 2, not Webhook 1. The row ID from Webhook 1's response links the two flows.

Self-hosted n8n adds one more issue: the default execution timeout is 60 seconds. A long Clay waterfall can hit that ceiling and leave the callback unhandled. In n8n settings, raise the execution timeout to at least 300 seconds for any workflow handling Clay callbacks.

Pricing and Plan Requirements

Clay's API access starts on the Starter plan at $149/month for 1,000 credits. The Free tier doesn't include API access. n8n Cloud starts at $20/month with 2,500 executions. Self-hosted n8n is free with no execution cap beyond your server capacity.

Clay's Explorer ($349/month) and Pro ($800/month) plans add more credits and additional waterfall providers. The API itself doesn't change across paid tiers. You're paying for credit volume and provider breadth, not additional API features.

Clay's API has rate limits that aren't clearly published, but in practice Starter accounts should stay under 5 concurrent requests. For batch imports in n8n, use the Split in Batches node with a Wait step to keep throughput at 3 to 4 rows per second. Hitting Clay's rate limit returns a 429, and your n8n workflow needs retry logic to handle it.

Frequently Asked Questions

Does Clay have a native n8n integration?

No. As of 2026, Clay doesn't have a dedicated node in n8n's library. You connect them using n8n's HTTP Request node and Clay's REST API. Setup takes about 45 minutes and doesn't require custom code.

Can n8n trigger Clay enrichment when a lead submits a form?

Yes. Connect a webhook-capable form (Typeform, HubSpot forms) to an n8n Webhook trigger. n8n filters the submission and posts qualifying leads to Clay's API. Clay enriches asynchronously and fires a callback to n8n when done.

Why is my Clay enrichment data blank in n8n?

Clay's enrichment is asynchronous. The POST response only confirms row creation. Configure Clay's outbound webhook in table settings to push enriched data to a second n8n Webhook node after the waterfall finishes. Without that two-webhook setup, enriched fields are always blank.

Does pre-filtering leads in n8n affect enrichment accuracy?

No. n8n is a routing layer and doesn't modify data before sending to Clay. Clay enriches whatever you send and adds fields from its waterfall providers. Filtering only controls which leads reach Clay.