A whole record from an email or a domain, by four routes, and only the in-CRM one needs Data Hub.
A Reverse Contact API key. The in-HubSpot route needs Data Hub Professional.
Contacts, Companies, one way, in.
Give it an email, a domain or a profile URL and it returns the person, their current role and the company behind it on one schema, which is what makes it safe to write into HubSpot properties rather than into a notes field somebody reads later. Four routes get it there, and the one people assume is cheapest usually is not: calling the API from inside a HubSpot workflow needs Data Hub Professional, because both the webhook action and the custom code action live in that hub rather than in Sales Hub. If you already own Data Hub, that route is the cleanest thing on this page. If you do not, Clay and n8n are not the fallback, they are the answer, and they cost less than the hub upgrade by a distance.
POST https://api.reversecontact.com/v2/enrich/persons Authorization: Bearer $RC_API_KEY Content-Type: application/json { "email": "j.okafor@northwind.io" } # one call, one record. no field mapping screen, # because the mapping is yours.
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 |
|---|---|---|
| Email to full person record | One way, in | POST /v2/enrich/persons resolves an email into identity, current role, history, education, skills and location. |
| Domain to company record | One way, in | POST /v2/enrich/companies returns firmographics and metadata for a domain or company name. |
| Live resolution | One way, in | The /live endpoints return a task id. Poll GET /v2/webhooks/:webhookId until status is succeeded, which is free and off the rate-limit clock. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer. Your pipeline decides what reaches HubSpot properties. |
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.
There is no field mapping screen here, because there is no app to hold one. What decides the shape of this build is which HubSpot feature carries the call, and the properties the answer lands in are ones you create and name.
| In HubSpot | In Reverse Contact | What to know about the match |
|---|---|---|
| Contact email | POST /v2/enrich/persons, 2 credits | The usual starting point, because a form submission carries an email and nothing else. Returns identity, the current role, history, education, skills and location on one schema, which is what makes it safe to write into typed properties. |
| Company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Run it on the company record rather than once per contact: one call covers every contact associated with it. |
| A profile URL already on the contact | POST /v2/fetch/persons, 1 credit | Half the price, and unmetered from the $249 plan rather than the $699 one. If any part of your stack already captures a profile URL, routing those contacts to this call instead is the largest single saving available on this pair. |
| A free freshness check first | POST /v2/fetch/persons/check, 0 credits | Says whether a profile is cached and when it was last updated, so the workflow chooses a 1-credit read or a 2-credit live refresh on evidence. Free in credits, and one more call inside the same 20 seconds. |
| A workflow secret | process.env.RC_API_KEY | Secrets are managed in the action definition and arrive as environment variables. The total length of all secret values in one action is capped at 1,000 characters. |
| require("axios") in a custom code action | The HTTP call itself | HubSpot pre-loads axios at ^1.2.0 among twelve Node libraries, including @hubspot/api-client at ^10 and lodash, so the action needs no dependency management of its own. |
| The callback() function | Output fields the workflow branches on | The documented way to pass data back into the workflow, and Node.js only. Return a match status alongside the values, because the workflow cannot otherwise tell a miss from a hit. |
| Anything outbound to Reverse Contact | Nothing at all | This is a read layer. No HubSpot property, contact or event is sent anywhere, and there is nothing in the product to send it to. |
These are HubSpot's own caveats about custom code actions rather than anything to do with enrichment, and each one works perfectly in a test on a single contact. The first is a correctness problem rather than a performance one, which is why it leads.
| What HubSpot documents | What it means for an enrichment action |
|---|---|
| Variables declared outside exports.main may be re-used by future executions | A response held in a module-level variable can be served to the next contact. Everything about a person belongs inside exports.main |
| A rate-limited call is retried only if you throw the error in the catch block | A 429 caught and turned into a tidy no_match is a contact silently left un-enriched, with the workflow reporting success |
| Actions must finish within 20 seconds and 128 MB | Comfortable for a cached lookup against a published 500ms P95. Impossible for a live refresh, which answers with a task rather than a record |
| The total length of all secret values is capped at 1,000 characters | One API key is nowhere near it. Worth knowing before a second and a third integration share the same action |
| Math.random is seeded by the current time, so executions can repeat | Only matters if you are sampling rows. HubSpot pre-loads random-number-csprng for the case where it does |
| Test logs report memory used and total runtime | The only place the distance to those two ceilings is visible, so read them before the workflow goes live rather than after |
A few 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 what hubspot documents rows and four documented exclusions, each one's note, and the six 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 variable re-use caveat is the line worth re-reading, because it is a correctness problem that no single-contact test can show you. Enrol two contacts at once and confirm each got its own answer, and the whole class of bug is either there or it is not.
The only question on the HubSpot side of this pair is whether you own Data Hub, and the grid is almost all one answer. Three of these five rows are identical, which is the finding rather than a formatting accident: upgrading Sales Hub buys nothing here, because the two actions that can reach an outside API live in a different hub altogether. Pick one on each side and the grid marks the answer.
Pick one on each side.
| What you own in HubSpot | A webhook action in a workflow | A custom code action in a workflow | The native Clay, Zapier or Make app | An n8n workflow on the CRM API |
|---|---|---|---|---|
| Free CRM or Starter | Not available | Not available | Available | Available |
| Sales Hub Professional, no Data Hub | Not available | Not available | Available | Available |
| Sales Hub Enterprise, no Data Hub | Not available | Not available | Available | Available |
| Data Hub Professional | Available | Available | Available | Available |
| Data Hub Enterprise | Available | Available | Available | Available |
Counted off that grid, of twenty pairings: fourteen give you available, six give you not available. Read down the first two columns and the recommendation writes itself. If you own Data Hub, call the API from a workflow and stop there, because it runs where the data already is and there is no third vendor to meter it or to break. If you do not, buying a hub to avoid a middle layer is the expensive answer: a Clay table or an n8n workflow does the same job against the CRM API that every tier already carries.
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.
HubSpot: Settings, Account and Billing
Both the webhook action and the custom code action require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. A team on Sales Hub Professional has workflows and still cannot call an outside API from one. This is the most expensive surprise on the pair and it is a purchase rather than a setting.
The five routes on this page
With Data Hub, a custom code action inside a workflow is the cleanest thing here. Without it, Clay and n8n are not a fallback, they are the answer, and both cost far less than the hub. Deciding this before you build means not discovering the gate halfway through a Flow somebody has already demoed.
HubSpot: Settings, Properties
Prefix them, so no rep ever types into one. Nothing in this build decides for you which property a value lands in, which is more work than a marketplace app and is also the reason this route never flattens a field somebody maintains by hand.
HubSpot: the custom code action, Add secret
Secrets are managed in the workflow action definition and arrive in the code as environment variables, read with process.env. The one documented ceiling is that the total length of all secret values in an action must not exceed 1,000 characters, which one API key will not trouble and three might.
HubSpot: callback() output fields
Reverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody is a normal outcome. Return a status through callback() and branch the workflow on it, rather than letting the write action run with nothing to write.
HubSpot: the custom code action
HubSpot documents that variables declared outside exports.main may be re-used by future executions of the action, to save memory. For an enrichment action that means one contact can be served another contact's response. Only a connection you genuinely want re-used belongs outside the function.
HubSpot: the catch block
HubSpot only retries a rate-limited call if you throw the error in the catch block in Node.js, or raise it in the except block in Python. A 429 caught and turned into a tidy no_match is a contact silently left un-enriched while the workflow reports success.
HubSpot: the action, Test
The test logs report how much memory the action used and its total runtime, which are the two numbers the 20-second and 128 MB ceilings are measured against. The output tells you the enrichment worked on one contact, which was never the thing in doubt.
The first step is the whole page and the other seven are an afternoon. That asymmetry is unusual here: on Salesforce the question is architectural, about callout ceilings and where a backfill lives, while on HubSpot it is a line on an invoice.
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/hubspot-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-reverse-contact.md
There is no app to install, so the first decision is which path the record takes. They differ in who maintains them, how many meters you are paying and whether the live endpoints are available to you.
The cleanest route, if you already own Data Hub Professional.
A contact-based workflow fires on form submission and a custom code action calls /v2/enrich/persons, reading the key from a workflow secret and returning HubSpot properties as output fields. Nothing sits between HubSpot and the data and there is no third meter. The catch is the hub: both the webhook action and the custom code action require Data Hub Professional or Enterprise, which is a separate purchase from Sales Hub. Custom code also has to finish inside 20 seconds and 128 MB, which rules out the live endpoints.
The default for most teams. No hub upgrade, fastest to change.
A Clay table reads a filtered HubSpot slice with a Lookup action, runs the Reverse Contact enrichment action on each row, and writes back with Update. Non-engineers can change the logic, and the same table can waterfall to another provider on a miss. The action runs on Clay credits by default, so this route needs no Reverse Contact account at all until you connect your own key to bill your own workspace.
When it has to be self-hosted, or the live endpoints matter.
An n8n workflow triggers on a HubSpot webhook, calls the API with an HTTP Request node, handles the async polling that a HubSpot workflow cannot, and updates the record with the native HubSpot node. Self-hosting means records never leave infrastructure you control, which is often the deciding argument.
The shortest no-code route, and new since September.
Reverse Contact maintains a Zapier app, so a Zap reads New Contact from HubSpot, calls Enrich a Person, and updates the contact with HubSpot's own action. No Data Hub, no code and no HTTP module to configure. The app bills 2 credits when a person is found and nothing when there is no match, which makes a miss free on this route. What decides whether it scales is Zapier's task meter rather than anything on this page.
A different job, not a cheaper pipeline.
Point an AI client at https://api.reversecontact.com/mcp and it gets thirty-seven tools: enrich and search for people and companies, the live variants, the search filter catalogues, Lists, Bulk, tasks and goals, and free checks on a profile, your usage and a running task. Paired with HubSpot's own connector, an agent can research an account and write the brief onto the record without anyone building a pipeline first.
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.
WhyBoth the webhook action and the custom code action require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. Workflows themselves are a Sales Hub feature and reaching outside them is not.
Price the hub against Clay and n8n before buying it. Full CRM API access is on every tier including the free one, so an external route reads and writes the same records without the upgrade.
WhyAn action must finish within 20 seconds and inside 128 MB of memory, and HubSpot returns an error on exceeding either.
Use the cached endpoints, which publish a 500ms P95. Arriving near 20 seconds means you are either calling a live endpoint, which answers with a task rather than a record, or looping over records inside one action.
WhyHubSpot documents that variables declared outside exports.main may be re-used by future executions of the action, to save memory, and many objects can be enrolled at the same moment.
Move every variable holding anything about a person inside exports.main. Only a connection you intend to re-use belongs outside it, which is the case the caveat was actually written for.
WhyA rate-limited call is only retried if the error is thrown. HubSpot documents that in Node.js you must throw it in the catch block, and in Python raise it in the except block.
Re-throw on a 429 instead of returning a no_match. A swallowed rate limit looks exactly like a real miss in the workflow history, which is what makes this one expensive to find later.
WhyNothing in this build decides that for you. The API returns a record and the property it lands in is whichever one your action names.
Write to prefixed properties only, then promote a value into a human-maintained property with a separate workflow that fires only where the human property is empty.
WhyReverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody completes normally rather than failing.
Return a match status from callback() as its own output field and branch the workflow on it. The call itself cost nothing, because every 4xx and 5xx is free.
WhyBelow 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Read quotas.workspace.credits.left from any response and alert on it. GET /v2/usage keeps answering when the checks do not, so a balance check never fails for the reason the lookup did.
Why/v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026.
Open the custom code action and change the path. A workflow action is not version-controlled by default, so the only copy of that string is the one inside it, and nothing will warn you.
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 2024 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.
that's a super frustrating situation, and honestly a pretty common headache with automated enrichment tools. Hubspot's native one can be a bit of a blunt instrument sometimes. It often matches based on weak signals, like just the company domain, and then grabs the first Jane Doe it finds on LinkedIn for that company. Unfortunately, there's no magic "undo" button for the whole batch.
r/hubspot·September 2025·6 points
The mechanism described here, matching on a weak signal and then taking the first plausible person, is exactly what returning null with a confidence score is for. This is one practitioner's account of one tool rather than a measurement, and the failure mode it describes is the reason every page in this directory treats a confident null as a feature.
You can export the property history for those messed up ones and restore the previous value. When you export property history you van filter the file for the date when you did the enrichment. When you redo the enrichment you can choose to only fill in the blanks rather than overwrite.
r/hubspot·September 2025·5 points
The most useful answer in that thread and the only one that gets the data back. The second half is the lesson rather than the fix: fill in the blanks instead of overwriting, which is the same rule as writing to prefixed properties and promoting separately. Taken in advance it costs nothing, and taken afterwards it costs an export.
How does HubSpot think about confidence matching? There are data points where 80% confidence is fine, but others where it really needs to be near certain to be useful. Are there any ways that customers can control the matching confidence interval? I'm also curious how much auditability there is to be able to trace back where a specific data point came from, or any ways to give it feedback when it misses
r/hubspot·September 2025·2 points
Asked in HubSpot's own Data Hub AMA, which is where somebody who had decided to buy the hub went looking for the feature. A controllable precision threshold and a last-updated timestamp on every record are both published API behaviour here, which is the difference between a product decision and an engineering one.
Then you would probably stand to benefit from other people's data. People who have concerns feel they have higher quality data that they do not want shared with other companies and competitors. This is a big deal because first party data is more valuable than third party data. Hubspot is a CRM. Not a data broker.
r/hubspot·July 2026·5 points
From a long argument about a HubSpot enrichment data-sharing change that HubSpot then reversed. The specifics have moved on and the question has not: whatever fills your records, somebody should be able to say where it came from and what else it feeds. Reverse Contact publishes its compliance position and a per-record update date, and the disclosure at the foot of this page states who wrote the page.
The main issue is that nobody updates contact information manually because it takes too much time and it's actually not their job.
r/CRMSoftware·January 2026·10 points
Opening a thread about a HubSpot database with missing titles and people who changed jobs months ago. It is worth quoting because it names the thing a licence conversation obscures: the alternative to an enrichment route is not reps doing it, it is nobody doing it, which is why the Data Hub question is worth answering rather than postponing.
Nobody discusses this pair by name, so the search was for the job: keeping HubSpot records current without reps typing. Two threads are worth more than the rest. One is somebody whose native enrichment matched the wrong person and could not be undone, and one is a HubSpot AMA where a customer asks for confidence scoring and provenance by name. Between them they describe the two things that separate a data layer from a tile in a marketplace.
Three of the five are about matching rather than about plumbing, which is the right emphasis on a pair whose plumbing is settled by one line on an invoice. The two tables above answer the plumbing; what the threads add is that the expensive mistake is not the route you choose but a provider that guesses, and a guess written into a property a rep owns is the one version of this that needs an export to undo.
The shortest version that actually runs. Credentials read from the environment rather than pasted inline.
// HubSpot workflow → Custom code action // Input field: email // Output fields: rc_status, rc_title, rc_company, rc_headcount // Secret: RC_API_KEY (read from process.env) const axios = require('axios'); exports.main = async (event, callback) => { const email = event.inputFields['email']; const res = await axios.post( 'https://api.reversecontact.com/v2/enrich/persons', { email }, { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } } ); const person = res.data?.data?.person; const company = res.data?.data?.company; // a miss returns null rather than a guess. write nothing, // flag it, and let a second provider take the row. if (!person) return callback({ outputFields: { rc_status: 'no_match' }}); callback({ outputFields: { rc_status: 'matched', rc_title: person.currentPosition?.title || '', rc_company: company?.name || '', rc_headcount: company?.employeeCount || 0 }}); }; # 20s and 128MB per run, so use the cached endpoint here. # /live returns a task to poll, which belongs in n8n.
What Reverse Contact gives HubSpot is one API with a consistent schema, webhooks for the asynchronous work, CSV for bulk, and an MCP server with 37 tools for agents. The shape of that is a layer other things are built on rather than a tile inside the CRM, which is why this page is four routes instead of one install guide. The practical gain is that nothing arrives with somebody else's field mapping, refresh schedule or definition of a good match. You decide which property a value lands in and whether it may overwrite what a rep typed, and a thin match comes back as null with a confidence score rather than as a plausible-looking row.
It also changes what you should compare it against. A marketplace enrichment app is a product decision: you accept its field mapping, its refresh schedule and its idea of what a good match is. An API is an engineering decision: you decide when it runs, what it is allowed to overwrite and what your pipeline does with a low-confidence answer. Reverse Contact leans into that by returning null with a confidence score instead of a best guess, and by letting you raise the precision threshold on the request, which is only an advantage if something in your stack is reading the score.
Which route is right comes down to one question, and it is not a technical one: do you own Data Hub Professional? If you do, call the API from a workflow and stop there, because it runs where the data already is and there is no third vendor to meter it or to break. If you do not, buying a hub to avoid a middle layer is the expensive answer, and Clay or n8n does the same job for a fraction of it. Reach for Clay when the logic will change monthly and a non-engineer owns it, and for n8n when the answer to "where does this record go" has to be "nowhere you do not control".
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 HubSpot, 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.
Not inside HubSpot, and that is deliberate rather than a gap. Five routes work: a HubSpot workflow calling the API directly, the native Zapier app as a step between two HubSpot steps, the native Clay app in a table that reads and writes HubSpot records, an n8n workflow or the verified Make app, and the MCP server for agent-driven work. Which one is right depends almost entirely on whether you own HubSpot Data Hub Professional.
Because calling an external API from a workflow means using either the webhook action or the custom code action, and HubSpot puts both in Data Hub rather than Sales Hub. A team on Sales Hub Professional has workflows and still cannot reach an outside API from one. This is the single most expensive surprise on this pair and it is a licence conversation, not a settings one.
Clay or n8n, in almost every case where you do not already own Data Hub. Both cost far less than the hub upgrade, and n8n self-hosts for nothing beyond the instance. Buying a HubSpot hub purely to avoid a middle layer is the expensive answer to this question.
In credits, which Reverse Contact publishes: 2 for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, and nothing for a freshness check. In money it depends on the pack or plan those credits came out of, and that conversion is yours rather than a number they print, so this page stops at the credit. Above roughly 15,000 lookups a month their own pricing page points you at an Unlimited plan, where the cached endpoints stop being metered at all.
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.