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

How the Reoon + Clay Connection Works

Reoon doesn't have a native Clay integration card as of mid-2026. You connect it through Clay's HTTP API enrichment block, which sends each email address to Reoon's verification endpoint and maps the JSON response back as new columns in your table. The connection is one-directional and credit-based: one Reoon credit per address verified, no reverse sync, no webhooks.

Clay's HTTP API enrichment block handles the full request-response cycle without needing Zapier or Make. It supports GET requests, dynamic field injection using Clay's formula syntax, and JSON path parsing for nested response objects. Reoon's API response is flat JSON, so parsing is quick once you know which fields to target.

Reoon's power mode does something no basic SMTP prober can: it makes actual delivery attempts to catch-all domains to determine whether a specific address receives mail, not just whether the domain accepts everything indiscriminately. That's the step Apollo's "Verified" label skips. Teams running Reoon alongside Clay catch 3-5% more invalid addresses than teams relying solely on Apollo's verification status, per internal testing across 8,000+ address sets.

Step-by-Step Setup: Connecting Reoon to Clay

You need three things before starting: a Reoon account with API access (any paid plan from $9/month), an active Clay workspace on the Starter plan or above, and a table with email addresses already populated. No third-party automation tool is required for this connection.

1. Get your Reoon API key. Log in to Reoon, navigate to Settings, then API. Copy the key. Don't paste it directly into a shared Clay workspace without using Clay's secret variable feature to avoid exposing it to collaborators.
2. Open your Clay table. Click the "+" column button at the far right of your column row to add a new enrichment column.
3. Select "HTTP API" as the enrichment source. It appears under "Other sources" in the enrichment library. Use the search bar to locate it faster if the list is long.
4. Configure the API request. Set the method to GET. Use this URL, replacing the column reference and key: https://emailverifier.reoon.com/api/v1/verify?email={{column.email}}&key=YOUR_API_KEY&mode=power. The column reference is case-sensitive, so match it exactly to your email column's display name in Clay.
5. Parse the response fields. Add six output fields using JSON path syntax: $.status, $.score, $.is_disposable, $.is_catchall, $.is_role_account, and $.mx_found. Name each column clearly in Clay, e.g., "Reoon Status" and "Reoon Score".
6. Add a pre-export filter. In Clay's filter bar, exclude any row where "Reoon Status" equals invalid, disposable, or risky before pushing to Smartlead, Instantly, or your sequencer. Segment unknown-status rows into a lighter-touch sequence rather than dropping them entirely.

Reoon Response Fields to Map in Clay

Reoon returns 12 fields per verification call. Most Clay teams only map the status field and miss the catch-all and score data that actually changes send decisions. The is_catchall and score fields together surface a category of bad addresses that a binary valid/invalid status won't catch on its own.

Don't skip the is_catchall field. A domain can return valid from basic SMTP probing and still be a catch-all that bounces 80% of real sends. Reoon's power mode detects this. Quick mode does not. If you're using quick mode to save time, you're not getting the verification accuracy you're paying for. Use power mode, full stop.

Common Errors When Connecting Reoon to Clay

Three setup problems cause 90% of failed Reoon + Clay runs. None of them appear in Clay or Reoon's official help documentation. These come from real troubleshooting sessions across Clay tables with 5,000+ rows running verification in production.

Rate limiting on large tables. Reoon's API allows 5 concurrent requests per API key by default. Clay's enrichment engine, running at full speed on a table with 200+ queued rows, will spike past that limit and start returning 429 errors. Fix: set Clay's concurrency to 3 in the HTTP API block's advanced settings. Not 5. Three. Clay's own processing overhead means 5 concurrent requests will occasionally exceed Reoon's cap during peak table runs.

The column formula not resolving. Clay's dynamic field injection is case-sensitive. If your email column is named "Work Email" in Clay, the formula reference is {{column.Work Email}}, not {{column.work_email}} or {{column.email}}. Check the column display name exactly before assuming the API request itself is broken.

Dropping all unknown-status addresses. Unknown status means Reoon couldn't reach a definitive result, usually because the receiving server timed out during power-mode probing. On most B2B prospect lists, 8-15% of addresses return unknown. Dropping them all from a 2,000-contact table means losing 160-300 potentially reachable contacts. Segment them into a lighter-cadence sequence and test before writing them off.

When to Run Reoon Verification in Your Clay Workflow

Run Reoon after email finding and before any outreach tool push. The right column order in a Clay table is: data source (Apollo, LinkedIn, or Clay native enrichment) then email waterfall finder then Reoon verification then export to your sequencer. Running Reoon earlier wastes credits on contacts that might not receive an email address from your waterfall at all.

If you're pulling emails from Apollo's export, you still need Reoon on any address Apollo marks as "Likely Valid" or "Guessed." Apollo's verification is SMTP-level and doesn't detect catch-all domains. On a real Clay table with 8,000 Apollo-sourced addresses, Reoon in power mode flagged 340 additional catch-alls that Apollo had already passed as valid, per an internal test run by the Modern Inbound team. That's 4.25% of the list that would have bounced.

For tables under 1,000 rows, run verification every time you refresh the list. For tables over 10,000 rows, run it once and cache the result in a dedicated Clay column. You're paying per verification, not per session. Re-verifying a stable list weekly burns credits on addresses that haven't changed.

Scale Outreach Without Hiring SDRs

Most B2B teams underestimate the work before sending: buyer-language research, list logic, DNS, warm-up, deliverability, copy testing, and reply handling. Modern Inbound runs the operating layer so founders can stay focused on sales calls.

Frequently Asked Questions

Does Clay have a native Reoon integration?

No. As of mid-2026, Reoon doesn't appear in Clay's native enrichment library. Connect it through Clay's HTTP API enrichment block using Reoon's REST API. Setup takes under 15 minutes and doesn't require Zapier or Make.

How many Reoon credits does this Clay integration use?

One credit per email address verified. Reoon's Growth plan gives 10,000 verifications for $29/month. For teams enriching 10K+ rows regularly, the Business plan at $79/month offers 50,000 verifications and a lower cost per credit.

What's the difference between Reoon quick mode and power mode?

Quick mode does basic SMTP probing and returns in under 1 second. Power mode adds catch-all domain detection and takes 3-8 seconds per address. For B2B prospecting, always use power mode. Quick mode misses 40-60% of invalid catch-all addresses, per Reoon's benchmark data.

Should I verify emails already marked as valid by Apollo?

Yes, for any address Apollo marks as "Likely Valid" or "Guessed." Apollo's SMTP verification doesn't detect catch-all domains. Reoon's power mode does. On a real test of 8,000 Apollo-sourced addresses, Reoon flagged 340 additional catch-alls that Apollo had already marked valid.