n8n and Reverse Contact
One way, inThe route that handles async resolution, and the one a security team signs off on.
- Moves: Contacts, Companies
- Needs: An n8n instance, self-hosted or cloud, and a Reverse Contact API key
Six integrations, and not one of them is gated by a plan on either side. What replaces the gate is ownership: somebody runs the instance, and every limit you hit belongs to the tool at the other end.
The iPaaS you can run on your own box.
n8n removes two arguments in one move. There is no per-task meter, because the community edition is self-hosted and free, and there is no data-residency conversation, because records never leave infrastructure you control. Every one of the six integrations here is in the usage cost band as a result, which makes this the only hub in the directory where the plan you are on never decides whether a pair is possible.
The HTTP Request node is why n8n turns up in pairings that have no native integration at all. Reverse Contact has no dedicated n8n node and does not need one, and the same is true of anything else with a documented API. It is also the only route in this directory that can sit and poll an asynchronous job, which is what the live enrichment endpoints return, because a CRM workflow and a Clay column both give up long before the answer arrives.
What you pay instead is attention. Every requirement on these six pages begins with an n8n instance, self-hosted or cloud, and two of them warn that the trigger takes a different credential from the node: the HubSpot trigger needs a registered public app rather than a service key, and the Slack trigger will not accept OAuth at all. The limits are borrowed too. HubSpot's daily cap is shared across every app on the account and Salesforce's allocation is finite, so the ceiling is theirs and the retry logic is yours.
n8n sits in the orchestration layer, with 3 other tools in this directory. Counted across the whole directory it reaches 6 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeThe route that handles async resolution, and the one a security team signs off on.
The cheapest way out of the Data Hub trap, and the trigger needs a public app.
Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.
Webhook out of the table, into a workflow that can wait for an async job.
The trigger needs a bot token and the node wants OAuth, so you build both.
One resource, one operation: create a post. That is the whole node.
4 things that decide whether a n8n integration will work for you, in the order they usually bite.
All six pairs here are metered by usage rather than locked behind a tier, which is unique in this directory. If a pair involving n8n is not working, the plan is not the reason, so do not start by looking at pricing. Start at the credential, then at the other vendor's API allowance.
A trigger and a node are separate connections in n8n and they frequently cannot share a credential. The HubSpot trigger needs a registered public app while the node takes a service key, and the Slack trigger refuses OAuth and wants a bot token. Both pages report the same symptom: the workflow runs perfectly when you execute it by hand and never fires on its own.
n8n's own ceiling is whatever your host and the target API allow, which means it has none worth planning around. What bites is HubSpot's daily cap, shared across every integration on the account, and Salesforce's finite API allocation, shared the same way. Budget those before you build a loop, because a backfill through n8n spends somebody else's quota.
A self-hosted instance is a server with your name on it. The Reverse Contact page says it plainly: you own the uptime, and a credit balance at zero stops even the free endpoints. Decide who gets paged before you move a production sync onto it, because the honest comparison with Zapier is not price, it is who answers when it stops.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
The route that handles async resolution, and the one a security team signs off on.
One way, in → 02The cheapest way out of the Data Hub trap, and the trigger needs a public app.
Two-way sync → 03Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.
Two-way sync → 04Webhook out of the table, into a workflow that can wait for an async job.
Two-way sync → 05The trigger needs a bot token and the node wants OAuth, so you build both.
Two-way sync → 06One resource, one operation: create a post. That is the whole node.
One way, in →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
No. Every pair documented here runs on the self-hosted community edition at no licence cost, and all six are in the usage cost band rather than behind a tier. Cloud plans are published on n8n.io/pricing if you would rather not run it yourself, and the choice between them is about who operates the box rather than about which connectors you get.
At docs.n8n.io, which covers the nodes, the HTTP Request node and credential handling. Credentials are stored per connection, so an n8n integration holds as many of them as it has steps that talk to something. There is no n8n API key in the sense of one key for the whole instance, which is the thing people are usually looking for when they search for one.
On these pages the commonest cause is the credential rather than the URL. A trigger does not use the node's connection, and two of the six integrations here need a different credential type for the trigger specifically: a registered public app for HubSpot, a bot token rather than OAuth for Slack. The tell is a workflow that works every time you run it by hand and never fires by itself.
n8n does not publish one, and that is the accurate answer rather than an evasion: on an instance you host, the ceiling is whatever your own machine and the target API allow. The numbers worth knowing are the other vendor's and they are on each pair page. Polling an asynchronous job is free of them in the one case that matters here, because a poll for a finished task is not a metered call.
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.