The route that handles async resolution, and the one a security team signs off on.
An n8n instance, self-hosted or cloud, and a Reverse Contact API key
Contacts, Companies, one way, in.
n8n is the only route in this directory that comfortably handles Reverse Contact's live endpoints, because those return a task to poll rather than a record. A HubSpot workflow cannot wait; an n8n workflow can, with a Wait node and a loop. Self-hosting also answers the question that stops several of these builds, which is whether customer records may leave infrastructure you control.
Method POST URL https://api.reversecontact.com/v2/enrich/persons Authentication Generic → Header Auth Name Authorization Value Bearer rc_your_api_key Body (JSON) { "email": "{{ $json.email }}" } # credentials live in n8n, not in the workflow JSON, # so the workflow is safe to export and review.
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 |
|---|---|---|
| Trigger | One way, in | A CRM webhook, a schedule, or a queue. n8n does not care which. |
| The call | One way, out | An HTTP Request node POSTs to /v2/enrich/persons with a Bearer token from credentials. |
| Async handling | One way, in | For /live, poll GET /v2/webhooks/:webhookId in a loop until status is succeeded. Polling is free and off the rate-limit clock. |
| Write-back | One way, out | The native HubSpot or Salesforce node updates the record with the mapped fields. |
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 node to configure, so the mapping here is between a Reverse Contact behaviour and the HTTP Request node option that handles it. Three of these options are off by default and two of those three are the difference between a workflow that branches on a miss and one that stops on it.
| In n8n | In Reverse Contact | What to know about the match |
|---|---|---|
| One HTTP Request node, POST | https://api.reversecontact.com/v2 | Every endpoint is reachable from the same node, which is why the absence of a dedicated node costs nothing. It also means no node update can break this workflow, and there is no predefined credential type to pick. |
| A Header auth credential | Authorization: Bearer rc_your_api_key | n8n's generic credential list carries Header auth alongside Basic, Digest, Query and the two OAuth types. Credentials live outside the workflow JSON, so the workflow stays safe to export and review. |
| Never Error, in Response options | A 404 or a 402, both of which cost nothing | The node reports success only on a 2xx by default, so a confident null stops the execution. Reverse Contact charges 0 credits on every 4xx and 5xx, so the miss was free and only the workflow needed telling about it. |
| Include Response Headers and Status | The status code, beside the body | Off by default, so the node hands back the body alone. With Never Error on you need the status to tell a miss from a rate limit, which makes these two options a pair rather than two independent choices. |
| Items per Batch and Batch Interval | The workspace minute limit | Reverse Contact applies a per-minute limit per workspace, reports it in quotas.minuteRateLimit on every response and answers 429 past it. Batching with an interval in milliseconds is how a bulk run stays underneath it. |
| A Wait node and a loop | POST /v2/fetch/persons/live, then GET /v2/webhooks/:webhookId | The live endpoints answer with a webhookId rather than a record. Poll until the status is succeeded, break on errored and read errorCode. Polling is free and does not count against the rate limit. |
| Pagination mode | POST /v2/search/people | Search answers in pages, and n8n exposes $pageCount and $response.body for the loop. People search is priced per profile delivered, so the free count endpoint should size the query before the pagination starts. |
| Timeout, in milliseconds | A published 500ms P95 on the cached calls | The node aborts a request that takes longer than this to begin responding. A short timeout is safe on the cached endpoints and wrong on the live ones, which are not slow so much as asynchronous. |
Every endpoint answers with the same five top-level keys, which is what makes one node enough for all of them. Four of them are the ones workflows skip and then need, and reading them in the workflow beats reading them in a dashboard a month later.
| In the response | What the workflow does with it |
|---|---|
| success | True when the request worked. An IF node on this alone is not a match test |
| data | The record, or null when nothing was confidently matched. This is the match test |
| error | Null on success, populated on the 4xx and 5xx responses that cost 0 credits |
| metadata.executionTimeMs | What this call actually took, worth logging against the published 500ms P95 |
| metadata.updatedAt | When this record was last updated. Decides whether a 2-credit live refresh buys anything |
| quotas.minuteRateLimit | limit, used, left and nextReset. Read it to pace a batch rather than retrying into a 429 |
| quotas.workspace.credits.left | The balance after this call. Branch on it and the workflow stops itself before a 402 |
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, seven in the response rows and four documented exclusions, each one's note, and the seven 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 options worth setting before anything else are Never Error and Include Response Headers and Status, because together they turn a confident null from a stopped execution into a path. Everything past that is ordinary HTTP, which is the argument for this route: there is no connector in the middle holding its own opinion about what counts as a good match.
None of this is a Reverse Contact tier. Every endpoint is available on every plan, and the question this page exists to answer is which host can carry which call, because the live endpoints hand back a task rather than a record and most of the routes in this directory have nowhere to put the wait. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Where the call runs from | Cached lookup inside one run | Live refresh, which returns a task | Records never leave infrastructure you control | A non-engineer can change it next month |
|---|---|---|---|---|
| n8n, self-hosted | Yes | Yes | Yes | No |
| n8n Cloud | Yes | Yes | No | No |
| A HubSpot or Salesforce workflow | With a caveat | No | With a caveat | With a caveat |
| A Clay column | Yes | No | No | Yes |
| A Zap or a Make scenario | Yes | With a caveat | No | Yes |
Counted off that grid, of twenty pairings: nine give you yes, four give you with a caveat, seven give you no. Only the two n8n rows are complete, and the column that completes them is the live one. If you never need a live refresh and nobody is asking where the records go, a Clay column or the native Zapier app is less to look after and somebody who does not write code can own it. Those two conditions are the whole case for this page, and both of them are procurement questions rather than engineering ones.
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.
n8n: deployment
The usual reason to choose this route over the Clay app or the Zapier app is that customer records may not leave infrastructure you control, and that is a deployment decision rather than a workflow one. The workflow is identical either way, so the question costs nothing to settle now and is awkward to revisit after a security review has started.
Your CRM: property names
The API returns a record and nothing writes it anywhere. That is more work than a marketplace app and it is exactly why this route never flattens a field a rep owns. Prefix the properties it writes, and promote a value into a human-maintained field with a separate rule or not at all.
Reverse Contact: Workspace, API Keys
Keys are created in Workspace then API Keys, and a per-key rate limit can hold one integration below the workspace maximum. This matters more here than on any other route: an n8n run goes as fast as the node allows, and the minute limit is shared with every other integration on the workspace.
n8n: Credentials, Header Auth
n8n recommends a Predefined Credential Type wherever one exists, and there is none for Reverse Contact, so this is the generic case: Header auth, with the name Authorization and the value Bearer followed by your key. Credentials are stored apart from the workflow JSON, which is what keeps the workflow safe to export, review and commit.
n8n: the node, Options, Response
Both are off by default. The node reports success only on a 2xx, so a lookup that matched nobody stops the execution, and without the status code you cannot tell that miss from a rate limit. Together these two turn an empty answer into a branch, and this is the step to take before the first real run rather than after it.
POST /v2/fetch/persons/check
Reverse Contact recommends this sequence itself: the check says whether a profile is cached and when it was last updated, so the workflow picks a 1-credit cached read or a 2-credit live refresh on evidence rather than on a guess. It is free, and the decision it enables is the main lever on this bill.
n8n: the node, Options, Batching
Items per Batch takes a count and Batch Interval takes a wait in milliseconds. Pacing a five-thousand-row run under the workspace minute limit is a two-field change here, and discovering the limit instead is a wall of 429s with a retry storm behind it.
n8n: a Wait node and an IF
Only the live and contact endpoints answer with a task. Read data.webhookId, then poll GET /v2/webhooks/:webhookId until the status reads succeeded, breaking on errored. Polling is free and off the rate-limit clock, so the loop costs wall clock and nothing else.
Steps five and seven are what separate a workflow that survives a bulk run from one that stops on row forty, and neither is about Reverse Contact. They are the HTTP Request node's own defaults, which assume an API that treats a miss as a failure. This one treats it as an answer, which is the point of it, and the node has to be told.
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/n8n-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/n8n-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.
WhyThe HTTP Request node reports success only on a 2xx by default, and a confident null is not a 2xx.
Turn on Never Error in the node's Response options and branch on the body with an IF node. The call cost 0 credits either way, so nothing was wasted except the execution.
WhyReverse Contact applies a minute limit per workspace, shared with every other integration on it, and answers 429 past it.
Set Items per Batch and a Batch Interval rather than adding a retry, and read quotas.minuteRateLimit for limit, used, left and nextReset. A per-key rate limit stops this workflow starving the rest of the workspace.
WhyA live job ends at succeeded or errored, and Reverse Contact documents the wait as usually seconds and possibly tens of minutes.
Break on errored as well as succeeded, read errorCode, and cap the loop. An uncapped Wait loop on a job that will not finish is an execution running until something external kills it.
WhyThe live endpoints are asynchronous by design. The response carries a webhookId rather than a record, which is what the documentation means by built to feed async pipelines rather than to block a request.
Read data.webhookId from the first call, poll GET /v2/webhooks/:webhookId until the status is succeeded, then take data.result. The polling is free and off the rate-limit clock.
WhyWhere a webhookUrl is used instead of polling, Reverse Contact keeps the credit on a delivery failure because the data was fetched, and reports the job as succeeded with a deliveryStatus naming the problem.
Poll the webhook id and collect the result you have already paid for. The four documented delivery failures are webhook-url-invalid, webhook-url-errored, webhook-url-timeout and webhook-url-unreachable.
WhyBelow 2 credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage, GET /v2/flags and webhook polling keep answering whatever the balance, so a balance check never fails for the reason the lookup did.
WhyReverse Contact replaced /v2/resolve with /v2/enrich and /v2/search/persons with /v2/search/people, and documented the old pair as live only until 13 October 2026.
Search the workflow JSON for both old paths and change them. A workflow exported before that date and imported after it fails on its first run rather than at deploy time, which is the worst moment to find out.
WhyPeople search is priced per profile delivered rather than per request, while company search is priced per page of up to 100 results, so the two are not the same arithmetic.
Call the free count endpoint to size a people search before you run it, and set the pagination limit deliberately. An unbounded pagination mode on a broad query is the expensive mistake on this endpoint.
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 2025 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.
[...] Running the cheap check first and only escalating qualified leads to Apollo is just good workflow economics.
r/n8n·May 2026·2 points
From a thread about putting a lightweight step in front of an expensive provider, which is the same shape as the free freshness check in front of a 2-credit refresh. Worth noting that the person is describing their own product in the rest of the comment, and that the pattern is sound regardless of who sells the cheap half.
The confidence scoring on the classification is smart - returning { category, confidence, signals } and tiering the Apollo query based on confidence is elegant. [...] The negative signal bucket is underrated too
r/n8n·May 2026·2 points
Two people designing from scratch the thing Reverse Contact already returns. Every response carries a confidence score and the precision threshold can be raised on the request, so the tiering this comment calls elegant is an IF node on a field rather than a classifier somebody has to build and maintain.
Are you going to share teh workflow? I am interested in checking this out. I have been trying to find enrichment options that are not subscription. I have a small quantity each month so does not make sense to have a subscription for enrichment api's
r/n8n·March 2026·2 points
A real constraint rather than a complaint, and the credit packs answer it: 5K to 1M credits with no subscription behind them. The catch is on the same page as the answer, which is that packs are valid 3 months, so lumpy volume cuts both ways.
Is it worth connection via api to paid company data bureaus like (Kompany, Moodys, etc)? You could set n8n up so that it's only pulling that info on the orgs you actually want it on as opposed to all.
r/n8n·May 2026·2 points
The same instinct as the first quote, applied to a different kind of provider. An IF node between a cheap filter and a metered call is the entire cost model of this route, and it is the one thing a workflow engine does that a CRM automation with a single linear path cannot.
If you're diving into lead enrichment, APIs are usually your best bet for reliability and accuracy. [...] For n8n, think about setting up a workflow that first checks the email domain for LinkedIn profiles, then uses a Google search node with some regex to filter out the right social accounts.
r/n8n·June 2026·2 points
The second half describes building identity resolution out of a search engine and a regular expression, which is the work a reverse lookup endpoint exists to not do. The comment goes on to recommend a manual review step for false positives, and that is the role the confidence score plays here instead.
Nobody discusses this pair by name, so the search was for the job: building an enrichment workflow in n8n and paying for it. Every thread is somebody doing exactly that, and the recurring conclusion is the same one Reverse Contact's own documentation reaches, which is to make a cheap call first and only escalate what passes. The threads are also candid about the cost of enrichment in a way vendor pages are not.
These five are the only set in the directory where the practitioners and the vendor documentation agree on the method rather than argue about the price: check cheaply, branch on confidence, escalate only what passes. That is also why this is the route that handles the live endpoints, because branching and waiting are the two things a workflow engine has and a CRM automation does not.
The shortest version that actually runs. Credentials read from the environment rather than pasted inline.
# 1. start the job: /live returns a task, not a record POST /v2/fetch/persons/live → { "webhookId": "wh_a1b2c3" } # 2. Wait node: 5 seconds # 3. poll. free, and off the rate-limit clock. GET /v2/webhooks/wh_a1b2c3 → { "status": "pending" } // loop back to step 2 → { "status": "succeeded", "data": { ... }} # 4. HubSpot node → Update Contact # this is the loop a CRM workflow cannot run, and the # reason the live endpoints belong here.
Every other route to Reverse Contact works on the cached endpoints, which return a record in the response. The live endpoints are different in kind: they hand back a task id and resolve in the background, which is the right design for fresh data and the wrong shape for anything that has to answer inside one HTTP request. That single fact is why n8n gets its own page here.
The second reason is procurement rather than engineering. A meaningful share of the teams who want this build are ones where a record leaving your own infrastructure is a conversation with a security team. A self-hosted n8n instance calling an API you already approved is a much shorter conversation than an iPaaS vendor holding your CRM credentials.
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 n8n, 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.
No, and you do not need one. The HTTP Request node with a header-auth credential covers every endpoint, takes about five minutes to set up, and cannot break when somebody else ships a node update. A dedicated node would save you one configuration screen.
Because the live endpoints are asynchronous. They return a task id and resolve in the background, so something has to poll GET /v2/webhooks/:webhookId until the status is succeeded. n8n does that with a Wait node and a loop. A CRM workflow cannot wait, and a Clay column is not built to.
Self-hosted if the reason you are here is that customer records may not leave infrastructure you control, which is the usual reason. n8n Cloud is fine otherwise and removes the pager. The workflow itself is identical either way.
Use an n8n credential rather than putting the header in the node. Credentials are stored separately from the workflow JSON, so the workflow stays safe to export, review and commit.
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.