n8n says it has 1,000+ integrations, fewer than Zapier's 8,000+ apps or Make's 3,000+. But n8n's reach is wider than the count: credential-only nodes, community nodes and the HTTP Request node let you connect almost any service with an API. Check your own app list rather than comparing headline numbers.
How many integrations does n8n have? n8n says it offers 1,000+ integrations, and its practical reach is wider, because credential-only nodes, community nodes and the HTTP Request node let you connect almost any service with an API. By headline count, that is fewer than Zapier's 8,000+ apps or Make's 3,000+, but the numbers measure different things. This guide explains what n8n counts, how to find any node, and how to judge coverage for your own stack.
Checked October 2026 against n8n's integrations page and integrations directory, n8n's docs on integrations and verified community nodes, Zapier's Apps help category and Make's integrations page. Counts change often. This is a guide built on published figures, not our own count.
Integration coverage is one of several factors when picking an automation tool, alongside pricing and hosting. For the bigger picture on AI and API costs, see our LLM API pricing comparison, and for how n8n stacks up overall, our n8n vs Zapier guide.
n8n number of integrations: what the figure includes
n8n calls its integrations nodes. Its docs group them into built-in nodes, which ship with n8n, and community nodes, which you install. Built-in nodes include app nodes for specific services, core nodes for logic and data handling, and credential-only nodes. The 1,000+ figure on n8n's website is a marketing headline for this catalogue, not a count of every way to connect.
| Type | What it is | Examples |
|---|---|---|
| Built-in app nodes | Nodes n8n ships for specific apps, with operations and often triggers | Slack, Google Sheets, HubSpot |
| Core nodes | Logic and utility nodes that work with any data | IF, Merge, Code, Schedule Trigger |
| Credential-only nodes | n8n handles auth; you call the API with HTTP Request | Services without a full node |
| Community nodes | npm packages built by third parties | Niche apps and partner integrations |
| HTTP Request node | Calls any REST API, with predefined or custom credentials | Anything with an API |
- 01Built-in node?
Use it
- 02Credential-only node?
HTTP Request with saved auth
- 03Community node?
Install if trusted
- 04Has an API?
HTTP Request, custom auth
- 05Still missing
Build a custom node
Credential-only nodes and the HTTP Request node
Credential-only nodes are the least understood part of n8n's catalogue. n8n's docs describe them as integrations where n8n supports setting up credentials for use in the HTTP Request node but does not provide a standalone node. You find them in the nodes panel like any other integration. In practice, they remove the hardest part of calling an API, which is authentication.
For services with no node at all, the HTTP Request node calls any REST API. n8n's docs describe two credential paths: predefined credential types for services n8n already supports, and generic credentials you configure yourself for anything else. Our guide to connecting any API in n8n walks through it.
Community nodes
Community nodes are npm packages built outside the n8n team. n8n's docs say instance owners and admins can install and manage them, and all members can use installed nodes. Verified community nodes show up in a More from the community section of the nodes panel. On n8n Cloud, owners can toggle their availability in the Cloud Admin Panel; self-hosted instances use environment variables.
If neither a built-in nor a community node fits, you can write your own. Our guide to n8n custom nodes covers the basics.
How many integrations does n8n have compared with Zapier and Make?
| Tool | Published count | Source |
|---|---|---|
| n8n | 1,000+ integrations | n8n.io (limitless integrations page) |
| Make | 3,000+ apps | make.com integrations page |
| Zapier | Over 8,000 apps | Zapier Help Center, Apps category |
Source: Vendor pages, checked October 2026
These figures are each vendor's own headline and are not counted the same way. A Zapier app and an n8n node may cover different numbers of operations and triggers. And n8n's HTTP Request node, credential-only nodes and community nodes extend its reach in ways a headline count does not capture. For a direct comparison of the other two, see our Make vs Zapier guide.
Where n8n coverage is strongest
n8n's integrations directory groups nodes into categories such as AI, communication, data and storage, developer tools, marketing, productivity and sales. Because n8n started as a tool for technical teams, its strengths lean towards developer tools, databases and AI: there are nodes for common databases, version control services, cloud storage and the major AI model providers, plus AI agent and vector store nodes for building assistants.
Where Zapier's larger catalogue tends to help is the long tail of niche business apps, where a pre-built connector saves a non-technical user from reading API docs. If your stack is mostly mainstream tools plus a few internal APIs, n8n's coverage is usually enough. If it is dozens of small vertical SaaS apps and nobody on the team is comfortable with APIs, check each one carefully before committing.
When the integration count actually matters
- It matters when your team cannot work with APIs and every app needs a ready-made connector with triggers.
- It matters less when someone can configure the HTTP Request node, because most modern apps publish a REST API.
- It barely matters when your workflows centre on a handful of core tools that every platform supports, such as email, spreadsheets, CRM and chat.
In short, treat the headline number as a rough signal, then check your own list. Ten minutes in the nodes panel tells you more than any count.
n8n nodes list: how to find what exists
- 1Search the nodes panel
In the editor; it includes built-in, credential-only and verified community nodes.
- 2Check the integrations directory
n8n.io/integrations, browsable by category.
- 3Read the node docs
n8n docs list each built-in node with its operations.
- 4Search npm
Use the n8n community node package keyword for community nodes.
- 5Check the app's API docs
If it has a REST API, the HTTP Request node can reach it.
n8n number of nodes vs depth of each node
A node count says nothing about depth. One app node might support a single action; another might cover dozens of operations and several triggers. When judging coverage, check the specific operations you need, such as create, update, search or a particular trigger, in the node docs. If an operation is missing, the HTTP Request node with the app's predefined credentials usually fills the gap without leaving n8n.
- List every app your workflows touch
- Check each for a built-in or verified community node
- Confirm the exact operations and triggers you need
- Note which ones need the HTTP Request node
- Check whether those apps have webhooks for real-time triggers
- Estimate maintenance for any community nodes
If you are building automations as a service or a product, our AI SaaS program covers choosing tools, building workflows and selling the results.
n8n integrations: FAQ
How many integrations does n8n have?
n8n advertises 1,000+ integrations on its website. That figure covers its built-in app nodes and related integrations. On top of it, you can install community nodes, and the HTTP Request node can call almost any service with an API, so the practical reach is wider than the headline number. Checked October 2026.
How does n8n compare with Zapier and Make on integrations?
By headline count, Zapier says it has over 8,000 apps and Make lists 3,000+ apps, while n8n says 1,000+. The comparison is not like for like: n8n lets you call any API with its HTTP Request node and pre-built credentials, and install community nodes, which narrows the gap for teams comfortable with APIs.
What are n8n credential-only nodes?
n8n's docs describe credential-only nodes as integrations where n8n supports setting up credentials for use in the HTTP Request node but does not provide a standalone node. They appear in the nodes panel like any other integration, and they let you call that service's API without handling authentication yourself.
What are n8n community nodes?
Community nodes are integrations built by people outside the n8n team and published as npm packages. Instance owners and admins can install them. Verified community nodes appear in the nodes panel and, per n8n's docs, can be installed directly from the canvas, including on n8n Cloud where the owner allows it.
Is there a full n8n nodes list?
Yes. n8n's documentation has a built-in nodes reference covering core nodes, app nodes and trigger nodes, and n8n.io has a searchable integrations directory by category. Community nodes are searchable on npm using the n8n community node package keyword.
Does a higher integration count mean a better automation tool?
Not by itself. What matters is whether the specific apps you use are supported, how deep each integration goes in operations and triggers, and what you can do when a node is missing. Check your own app list against each tool before choosing on headline numbers.
Connect anything, then build something people pay for.
The AI SaaS program, included in All Access, covers automation, AI agents and building sellable AI tools, with the other three programs, live coaching and the private community in one subscription.
Free automation updates
Join the free Telegram channel for n8n, Make and AI tool changes as they happen.