Four native actions on Clay credits, and no Reverse Contact account needed to start.
A Clay account. Your own Reverse Contact key is optional and changes which meter you spend.
Contacts, Companies, one way, in.
This is the shortest path in the directory between Reverse Contact and a CRM, and the only one that needs no Reverse Contact account to try. The app is one of four enrichment actions you pick from a menu, and from there Clay's own CRM integrations carry the result the rest of the way. It is also the right place to put Reverse Contact in a waterfall, because returning null with a confidence score gives the next step something honest to branch on. Build the HTTP column instead when you want an endpoint the four actions do not expose, or the raw response in front of you while you tune the request.
# Column type: HTTP API Method POST URL https://api.reversecontact.com/v2/enrich/persons Headers { "Authorization": "Bearer rc_your_api_key", "Content-Type": "application/json" } Body { "email": "/Work Email" } # "/Work Email" is a Clay column reference, so every # row posts its own address. that is the whole setup.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Clay to Reverse Contact | One way, out | The native action takes the row's email, name, company or profile URL. An HTTP API column POSTs to /v2/enrich/persons or /v2/enrich/companies instead. |
| Record back to the column | One way, in | The full structured profile lands as JSON, and you map the fields you want into their own columns. |
| Confidence and nulls | One way, in | A miss returns null with a confidence score rather than a guess, so a conditional run can decide what happens next. |
| Onward to the CRM | One way, out | Clay's HubSpot or Salesforce Update action writes the mapped fields back. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
Four actions, and which one you want is decided by the identifier you already hold rather than by what you want back. Two start from an email or a domain, two start from a profile URL, and Clay publishes a different output field list for each.
| In Clay | In Reverse Contact | What to know about the match |
|---|---|---|
| Find Professional Profile | Reverse lookup from an email, 2 credits | Takes any combination of Email, Full name, Company name and Company domain, and Clay states that more fields improve match accuracy. Returns the ID, Public ID, LinkedIn URL, first and last name, headline, current position title, current company name and ID, and an update date. |
| Find company professional profile | Reverse lookup from a domain, 2 credits | Company domain is the only required input. Returns the company ID and name, industry, tagline, website URL, employee count and count range, follower count, an update date, and a city and country. |
| Enrich professional profile | Cached lookup from a profile URL, 1 credit | Clay lists ID, Public ID, Member ID, LinkedIn URL, first and last name, headline and summary, while the action description also promises experience, education and skills. Open the action in your own table before designing a column around the longer list. |
| Enrich company profile | Cached lookup from a profile URL, 1 credit | The fullest output of the four: description, tagline, logo and background URLs, employee count and range, followers, headquarter, specialities, locations, founded date and a phone number. |
| An HTTP API column | Any endpoint, on your own key | The route to everything the four actions do not expose, including the free freshness check and the live endpoints. Clay's plan comparison puts HTTP API integrations on Growth and above, so this is the one half of the pair with a real tier gate. |
| Only run if | A condition, not a field | Where the waterfall is actually built. The column runs only where the condition holds, so a second provider is charged for the rows this one left empty rather than for the whole table. |
| The write into a CRM | Not Reverse Contact's job | Clay's own HubSpot or Salesforce Update action carries the mapped columns the rest of the way, and Clay marks CRM integrations as a Growth feature. Nothing travels back to Reverse Contact from here at all. |
| A phone number or a verified email | Separate endpoints, not Clay actions | Reverse Contact prices a direct phone at 20 credits and a business email at 3, each charged only when one is found. Neither is one of the four actions, so both need an HTTP column or a different route entirely. |
The credit price per call is published and a dollar rate per lookup is not, so the credit is the only unit this page prints. On the native app you are usually spending Clay credits instead, and the figures below are what you spend from the moment you connect your own key.
| The call | What it costs, and what that buys |
|---|---|
| Freshness check, /fetch/*/check | Free. Says whether a profile is cached and when it was last updated, which is the call Reverse Contact recommends making before you spend anything |
| Cached lookup from a profile URL, /fetch/* | 1 credit. The two Enrich actions |
| Reverse lookup from an email, a name or a domain, /enrich/* | 2 credits. The two Find actions |
| Live refresh, /fetch/*/live | 2 credits, and not reachable from a column: it answers with a task id rather than a record |
| A lookup that matches nobody, or any other 4xx | Nothing. Reverse Contact charges 0 credits on every 4xx and 5xx response |
| That same miss, paid in Clay credits | One Action. Clay counts each record enriched as 1 Action regardless of data source or provider |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six the call rows and three documented exclusions, each one's note, and the eight vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The two-step shape is the part worth planning around. An email buys you identity and a current job title; the experience, education and skills behind it come from a second action run on the profile URL the first one returned. That is two columns and 3 credits for one complete person, and it is not what a four-action list looks like at a glance.
Reverse Contact is not the gated part. Clay lists every one of its actions as Included in All Plans, so the lookup itself runs on a Free workspace, and the tiers begin on everything you would do with the answer afterwards. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Clay plan | Run the four Reverse Contact actions | Schedule recurring enrichment runs | Reach an endpoint the actions miss, over HTTP | Write the result into HubSpot or Salesforce |
|---|---|---|---|---|
| Free | Included | Not included | Not included | Not included |
| Launch | Included | Included | Not included | Not included |
| Growth | Included | Included | Included | Included |
| Enterprise | Included | Included | Included | Included |
Counted off that grid, of sixteen pairings: eleven give you included, five give you not included. So this pair is free to evaluate and $446 a month to operate, and every gate in it belongs to Clay rather than to Reverse Contact. If that Growth line is the only thing between a working table and a populated CRM, an n8n workflow does the same write for the price of the instance and the native Zapier app does it by the task.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Clay: pricing
Clay's catalogue marks every Reverse Contact action Included in All Plans, so the lookup runs on a Free workspace. Its plan comparison puts CRM integrations and HTTP API integrations on Growth, listed at $446 a month. You can therefore measure the match rate for nothing and still have nowhere to deliver the answer.
Clay: Add enrichment, Select Reverse Contact account
The modal asks you to pick an account. Leave it on the Clay-provided key and the lookups spend Clay credits. Click + Add account and authenticate, and they bill your own Reverse Contact workspace instead. Both work on every plan, and the choice decides which bill grows and whose usage dashboard shows the calls.
Clay: Integrations, Reverse Contact
Find Professional Profile starts from an email, Find company professional profile from a domain, and the two Enrich actions from a profile URL. Clay documents a different required input and a different output list for each, so they are not interchangeable, and the wrong one returns a thinner record rather than an error.
Clay: column names
Prefix them, the way the CRM pairs prefix a property. The column a later Update action maps into your CRM is what decides whether a rep ever loses a field they typed, and renaming columns after the write step is mapped is tedious rather than hard.
Clay: the cell, Expand
This is the whole reason to use a table rather than a pipeline. The response carries an update date and a confidence score alongside the fields, and reading those on ten real rows of your own list tells you more than any published match rate can.
Clay: a second enrichment column
Find Professional Profile returns identity, the current title and the current company. Experience, education and skills come from Enrich professional profile, run on the LinkedIn URL the first action returned. Two columns, and 3 credits in total on your own key.
Clay: run settings, Only run if
This is what makes a waterfall a waterfall: the next provider touches only the rows this one left empty. Reverse Contact returning null rather than a best guess is what gives the condition something honest to test, so the two features suit each other exactly.
Clay: run settings, Auto-update
Clay documents it as re-running the enrichment when the source data changes, so an edit to any column it reads is a re-run and a 2-credit action becomes a standing cost. Turn it on once the upstream columns have stopped moving.
Six of those eight are decisions rather than clicks, and the two that cost money if taken late are the first two. That is the usual shape on the orchestration layer, where the tool is ten minutes and the economics are the design.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/clay-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyReverse Contact returns null rather than a best guess when it is not confident, and puts a confidence score on every response. An empty cell is the documented answer rather than a failure.
Treat empty as a branch instead of an error. Put Only run if on the next provider's column so it picks up exactly the rows this one left blank, which is the whole mechanism of a waterfall.
WhyClay documents a different output list per action, and the one that starts from an email returns identity, the current title and the current company rather than experience, education and skills.
Chain Enrich professional profile onto the LinkedIn URL the first action returned. Two columns, and 3 credits in total once you are on your own key.
WhyClay's plan comparison marks CRM integrations as a Growth feature while the Reverse Contact actions are Included in All Plans, so the lookup and the delivery are gated at different tiers.
Check the plan before you debug the mapping. On Free or Launch the write action is not there to configure, which presents as a broken column rather than as a missing tier.
WhyClay states that each record enriched or exported counts as 1 Action regardless of data source or provider, so a miss costs the same Action as a hit.
Filter the import step down to the rows actually missing the field, and connect your own Reverse Contact key if misses dominate: a 4xx costs 0 credits there, so on that meter a miss is free.
WhyThe Clay listing carries four actions, the two Find and the two Enrich ones. The free check endpoints are not among them.
Reach them through an HTTP API column, which Clay puts on Growth and above. Checking first and fetching second is the sequence Reverse Contact's own documentation recommends for saving credits.
WhyThe live endpoints are asynchronous by design. They reply with a webhookId and deliver the result afterwards, and Reverse Contact documents that this usually takes seconds and can take tens of minutes.
Keep the cached actions in the table and run live resolution where a poll loop is ordinary. Polling is free and off the rate-limit clock wherever you do it, so the cost of moving it is the workflow rather than the call.
WhyWhen a Reverse Contact workspace drops below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage and webhook polling keep working whatever the balance, so a balance check never fails for the same reason the lookup did.
WhyAuto-update is documented as re-running the enrichment whenever the source data changes, so an edit to any column it reads counts as a change.
Turn auto-update on last, after the upstream columns have settled, and leave Only run if on the column so even a re-run stays conditional.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
yeah that's kinda normal. clay isn't a lead source itself, it's more like an enrichment/automation tool. you still gotta pull leads from somewhere like linkedin, apollo, or storeleads and then use clay to clean, enrich, and build workflows. def don't rely on clay alone to find prospects
r/LeadGeneration·May 2025·3 points
Answering somebody who had noticed that Clay holds far less data than LinkedIn does. It is the clearest statement of why this pair exists at all: the table is the workflow, and something underneath it has to be the data. Which provider goes underneath is the only decision this page is about.
Clay can be your main enrichment engine for list building, but only if you pair it with solid data sources and strict verification. Do a bake-off: sample 150 target accounts across regions, then compare Apollo, UpLead, and People Data Labs on match rate, direct dials, GDPR flags, and bounce rate [...] If coverage is within 10-15% of ZoomInfo and your bounce stays under 3%, cut ZoomInfo.
r/gtmengineering·December 2025·3 points
The thresholds are this person's own rather than anybody's standard, and the method is the point. It is also exactly what Reverse Contact says to do with its own published number: 70%+ is a global identity match rate and your list is not the global corpus. A table is the cheapest place there is to run a bake-off, which is the strongest argument on this page.
One thing I've seen with Clay is that it feels expensive when you use it like a bulk data provider, but much more reasonable when you use it as a filter first. I rarely enrich everything. I narrow the list with cheap signals and firmographics, then only run waterfall email/phone on leads that actually look worth it. That shift alone cut my credit usage a lot, and the outreach quality went up because fewer bad leads made it through. At that point you're paying for decisions, not just data.
r/gtmengineering·January 2026·16 points
The best description of Only run if anywhere in these threads, and it was arrived at from a bill rather than from documentation. Paying for decisions rather than for data is also the honest answer to the complaint two quotes below.
Instead of pulling from Clay's built in data marketplace, bring your own API keys. When you use your own data API you're paying the provider directly without Clay's markup on top. [...] The thing that will create the most problems is action credits, part of the new pricing system Clay just rolled out. Every workflow step, every HTTP request, every CRM push burns credits and there's not much you can do about that at agency scale
r/techsales·April 2026·3 points
From somebody running outbound for eight to ten clients, which is where this arithmetic stops being theoretical. It matches the table above exactly: connecting your own Reverse Contact key moves the data half of the bill onto your own workspace, where a 4xx costs nothing, and leaves the action half precisely where it was.
they pay all the data provider fees. you just pay them for credits to use those providers, so it's more efficient for the end buyer. TLDR my TLDR? It's like going to a carnival and buying some tickets to ride the rides you want, instead of contracting every single ride operator for more rides than you realistically need.
r/sales·September 2024·13 points
The clearest account of the default arrangement in any of these threads, and it is why the four Reverse Contact actions run with no Reverse Contact account behind them. What the analogy hides is in the table above: on Clay's meter you pay for the ride whether or not you get on it, and on Reverse Contact's own meter a miss costs nothing.
Nobody discusses this pair by name, so the search was for the job instead: what a Clay table needs underneath it, and whether the data already in it is any good. The threads are blunter than any vendor page and they agree on one thing, which is that Clay is a workflow engine rather than a data source. The arguments are about price and about freshness, and both of those have a published answer rather than an opinion.
Four of the five are about the data rather than about the integration, which is the right thing to be arguing about: the column is ten minutes of work and the provider under it is the decision. The claim worth checking against the grid above is the pricing one, because every gate on this pair is Clay's rather than Reverse Contact's, and an n8n workflow removes all of them for the price of the instance.
The shortest version that actually runs. Credentials read from the environment rather than pasted inline.
# pull the fields you want out of the JSON column Title /Reverse Contact.data.person.currentPosition.title Company /Reverse Contact.data.company.name Headcount /Reverse Contact.data.company.employeeCount LinkedIn /Reverse Contact.data.person.linkedInUrl # then the conditional that makes a waterfall a waterfall: # run the next provider only where this one came back null. Run if /Title is empty # finally: HubSpot → Update Contact, ignore blank values, # writing to rc_* properties your reps never type into.
The reason to run Reverse Contact through Clay rather than straight into a CRM is not speed, it is iteration. In a table you can see the raw response next to the row, change the request, re-run fifty rows and look at what came back. That loop is how you find out what your actual match rate is on your actual list, which is the only number that decides whether a data provider is right for you and the one nobody publishes.
Once you know it, the question becomes whether Clay stays in the path. If the logic settled and an engineer owns it, a direct API call from the CRM is cheaper and has fewer moving parts. If the logic keeps changing, or a non-engineer owns it, the table is worth its actions. Both are defensible; drifting into a pipeline nobody has touched in six months is not.
Where Clay is unambiguously right is the waterfall. Reverse Contact returning null with a confidence score rather than a best guess is exactly the input a conditional run wants: cheap source first, Reverse Contact on what it missed, a third provider on what is still empty, and each step only touching the rows the previous one could not resolve.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Clay, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Pick it from the enrichment actions. There are four: find a person behind a work or personal email, find a company from a domain, enrich a person from a profile URL, and enrich a company from its profile URL. Clay marks all four Included in All Plans, so they run on a Free workspace, and classifies the listing as a Clay-built Integration rather than a vendor-maintained one, which is worth knowing because it decides who fixes it. An HTTP API column is still the route for anything the four do not cover, such as the free freshness check and the live endpoints.
Iteration. In a table you can see the raw response next to the row, change the request, re-run fifty rows and look at what came back. That loop is how you find your real match rate on your real list, which is the only number that decides whether a data provider suits you and the one nobody publishes.
Not on the native app, by default. It runs on Clay credits unless you connect your own Reverse Contact key, in which case the lookups bill to your Reverse Contact workspace instead and you are back to one meter, theirs. Either way Clay bills the attempt rather than the result, so a row that misses still costs you something, which is the argument for putting the cheapest high-coverage source first in a waterfall.
Not comfortably. The live endpoints return a task id to poll rather than a record, and a column is not built to wait. Use the cached endpoints here and run live resolution in n8n, where a polling loop is natural.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.