Clay + Make Integration 2026: Complete Setup Guide for B2B

How Clay and Make Work Together

Clay enriches contacts from 75+ data sources and fires a webhook when a table row completes enrichment. Make catches that webhook, parses the JSON payload, and routes the contact to any downstream tool: CRM, outreach platform, Slack, or Google Sheets. The integration runs bidirectionally via Make scenarios, triggered on enrichment completion, with no coding required.

Clay is a data transformation layer. It's not built to push records into your outreach tool or CRM on its own. Clay without an automation layer is expensive data that goes nowhere. Make fills that gap. When Clay finishes enriching a batch of 500 accounts, Make fires immediately and moves those contacts wherever they need to go, not hours later when someone remembers to export the table.

One recruiting SaaS team using this setup cut their weekly ops time by 9 hours per week, per internal Modern Inbound client data across 18+ active outbound programs. The data flow: Clay row enriches, webhook fires to Make, Make parses the JSON, conditional logic routes by job title or company size, record lands in the right tool automatically.

Step-by-Step Setup Guide

Setting up Clay and Make takes 45 minutes with webhook experience, 90 minutes without. You don't need a third-party connector. Clay sends enrichment output to a Make webhook URL via its built-in integration action. Make parses the payload and routes it. Both platforms need paid plans for this to work in production.

1. Generate API keys. Go to Clay Settings > API > Generate Key. Store it for advanced scenarios where you want Make to trigger Clay table enrichment via API, not just receive it.
2. Create a Make webhook. Open Make, start a new scenario, add a "Custom Webhook" trigger module. Copy the webhook URL it generates. This is the address Clay will send enrichment data to.
3. Add the webhook action in Clay. In your Clay table, open the Integrations panel, select "Send to Webhook," paste your Make webhook URL, and choose which columns to include in the payload.
4. Map fields in Make. Run a test enrichment in Clay for one record. Make auto-detects the JSON structure. Map Clay output fields (email, company, LinkedIn URL, job title, enrichment source) to your destination app's input fields.
5. Set deduplication rules. Add a "Search Records" module in Make before any create or update step. Search by email. If a match exists, update. If no match, create. Skip this and you'll have duplicate CRM records within 48 hours.
6. Test with 5 sample records. Don't run your full Clay table yet. Run 5 records, check each destination for accuracy, verify field mapping held across all 5. Fix before scaling to the full list.
7. Enable and monitor for 48 hours. Watch Make's scenario run history and Clay's webhook delivery log. API rate limits hit hardest in the first 48 hours of a bulk enrichment run. If you see 429 errors in Make, add a delay module between steps.

One edge case that catches everyone: if Clay returns a null value for an enrichment field, it still passes that null to Make as an empty string. Your destination app may reject empty required fields or create blank records. Add a Make filter that skips any record missing your minimum required fields before it reaches the create step.

Field Mapping Between Clay and Make

Clay outputs every enriched column as a JSON key. Make receives the full object and lets you map each key to a destination field via drag-and-drop. The most common mismatch is column naming: Clay sends "First Name" with a space, but most CRMs expect "first_name" with an underscore. Fix this in Make's field mapper before your first full table run.

Waterfall enrichment in Clay complicates field mapping slightly. When Clay tries Apollo first, then Clearbit, then Hunter, the output field may carry data from any of the three. Add a "Source" column in Clay that logs which provider filled each field, then map that to a custom CRM field. You'll have data provider attribution within 30 days, which matters when it's time to cut underperforming enrichment sources.

Top Use Cases for the Clay and Make Integration

The three highest-ROI patterns with Clay and Make are: routing enriched contacts directly into an outreach sequence, triggering Slack alerts when a target account hits a revenue or headcount threshold, and sending enrichment failures to a review queue instead of silently dropping them. Most teams only set up the first one and miss the other two entirely.

Routing to outreach sequences. When Clay finishes enriching a contact, Make fires and adds them to a Smartlead or Instantly campaign automatically. Teams running 500+ outreach emails a week report eliminating manual list imports entirely. The time savings compound: 30 minutes saved per day is 130 hours recovered per year.

ICP scoring triggers. Add a Clay formula column scoring contacts 1 to 10 based on title seniority, company size, and tech stack. Set a Make filter to pass only contacts scoring 7 or higher to your primary outreach sequence. Everything else routes to a nurture sheet or a lower-touch campaign. You'll book fewer unqualified meetings and close more of the ones you do take.

Enrichment failure routing. Clay can't always find an email or phone number. Instead of losing that account, route null-email records to a "needs review" Notion database or Google Sheet. Don't throw away a warm ICP account because Clay struck out on one enrichment pass. A team member can run that contact through a different tool or attempt a manual lookup.

Pricing and Plan Requirements for This Integration

Clay's webhook integration is on the Starter plan at $149/month. Make's free plan caps at 1,000 operations/month, which covers testing but breaks under production volume. Teams enriching 500+ contacts a week with a 5-step Make scenario hit roughly 20,000 operations a month, which requires Make's Pro plan at $29/month (150,000 operations).

Here's the honest cost math: Clay Starter ($149) plus Make Pro ($29) equals $178/month for a fully automated enrichment-to-CRM workflow. The alternative is 2 to 3 hours a week of manual work. At a $60/hour internal ops cost, that's $480 to $720/month in labor. The integration pays for itself in month one, not month six.

One caveat: if you're running Clay's waterfall enrichment with 5+ providers per row, your Clay credits burn faster than the Starter plan covers. Most teams enriching at scale need Clay's Explorer plan at $349/month. That's still cheaper than hiring someone to manage the same workflow manually.

Want Research-Led Outreach Run For You?

Modern Inbound mines buyer language, builds account lists, writes outreach, manages client-owned inboxes, and routes qualified replies. Your team gets sales conversations, not another tool to operate.

Frequently Asked Questions

Getting Started

The webhook setup takes under an hour. If you're already using Clay for enrichment, the only question is what happens with the data after it's enriched. If the answer is downloading a CSV and uploading it somewhere else, you're 45 minutes away from never doing that again.

If you'd rather skip building and managing this yourself, that's what Modern Inbound does. We handle enrichment, outreach infrastructure, and campaign execution end to end. Get in touch to see if we're a fit.