n8n integrations

n8n integrations, and the instance somebody has to own

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.

n8n.io 6 integrations
layerOrchestration
entry$0 self-hosted
authCredentials stored per connection
automationWorkflows on cron, webhook or qu...
verified2026-09-18
checked Guides written 6 of 6
6integrations checked
0built natively
4sync both ways
1need a plan upgrade
The short version

What decides a n8n integration

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.

All 6

Every n8n integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 6 of 6
←
BuiltBuilt on the APIZapier, Make or n8n
WatchNo app, you build it

The 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
Metered by usage · hours Read the guide
↔

n8n and Salesforce

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.

  • Moves: Contacts, Companies, Deals, Tasks, Custom objects
  • Needs: An n8n instance, a Salesforce edition with API access, and an External Client App
Metered by usage · hours Read the guide
↔

n8n and Clay

Two-way sync
BuiltBuilt on the APIZapier, Make or n8n
WatchNo app, you build itNeeds a higher plan

Webhook out of the table, into a workflow that can wait for an async job.

  • Moves: Contacts, Companies
  • Needs: An n8n instance, and Clay Growth or above, because both halves of this pair are Growth features
Needs a higher plan · hours Read the guide
↔

n8n and Slack

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

The trigger needs a bot token and the node wants OAuth, so you build both.

  • Moves: Messages
  • Needs: An n8n instance you host or rent, and a Slack app with the right token type
Metered by usage · hours Read the guide
←

n8n and LinkedIn

One way, in
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

One resource, one operation: create a post. That is the whole node.

  • Moves: Messages
  • Needs: An n8n instance and a LinkedIn app. Company posts need the organisation URN.
Metered by usage · minutes Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a n8n integration will work for you, in the order they usually bite.

01

The gate is never n8n

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.

02

Expect two credentials, not one

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.

03

The rate limit you hit belongs to the other vendor

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.

04

Somebody owns the uptime

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.

Written up

The n8n integrations with a full guide

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.

Other tools

Integrations for the rest of the stack

Connecting n8n is half the job

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.

FAQ

n8n integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Do n8n integrations need a paid plan?

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.

Where is the n8n API documentation?

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.

Why is my n8n webhook not working?

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.

What are n8n's rate limits?

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.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 6 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

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.

Ask an assistant