An automation tool is only as useful as the systems it can connect to. If a workflow can’t reach your CRM, your database, your messaging tools, and the custom systems your business depends on, it won’t save you much real work. That’s why integrations sit at the center of any automation platform, and it’s one of n8n’s biggest strengths: it connects to hundreds of apps out of the box, and to almost anything else by calling any API or running custom code.
An n8n integration is a connection between n8n and another application that lets a workflow read data from it, write data to it, or respond to events inside it. Integrations are what allow n8n to capture a new lead from a form, enrich it with a data service, add it to your CRM, and notify your sales team, all in a single automated flow. The more apps n8n can reach, and the deeper those connections go, the more of your day-to-day work it can actually take over.
This guide is for anyone deciding whether n8n is the right fit for their business. It covers what integrations are and how they work, how many apps n8n connects to, the differences between native, community, and custom integrations, how to connect the custom and legacy systems that matter most, how AI integrations work, and how to build n8n integrations that stay reliable instead of breaking easily.
What Are n8n Integrations?
In n8n, an integration is delivered through a node: a building block on the workflow canvas that represents a specific app or service. Drop the Slack node into a workflow and it can send messages; drop the HubSpot node in and it can create or update contacts. Each node knows how to talk to its app, so you configure what you want rather than writing the connection code yourself.
Integrations come in two flavours that matter. A trigger integration starts a workflow when something happens in an app, such as a new email arriving or a new record being created. An action integration does something in an app as a step in the workflow, such as adding a row, sending a message, or fetching data. Most apps offer both, so a single workflow can be triggered by one app and take actions across several others. Connecting the integration to your account is handled through credentials, which you set up once and reuse securely across workflows.
How Many Apps Does n8n Integrate With?
n8n ships with more than 400 built-in integrations covering the tools most businesses use, browsable in the n8n integrations library. But the more important number is effectively unlimited, because when a ready-made node does not exist, n8n’s HTTP Request node can call any service that has an API, and almost every modern service does.
This matters more than it used to. According to Postman’s State of the API Report, which surveys thousands of developers, the overwhelming majority of organisations are now API-first, and the average application is powered by dozens of APIs. In other words, the software your business runs on is built to be connected. n8n’s ability to reach any of those APIs means the real question is rarely can n8n integrate with this, but how best to do it.
How n8n Integrations Work
Under the hood, an n8n integration does three things: it authenticates with the app, it sends or receives data, and it hands that data to the next node in the workflow. Understanding this makes it clear why some integrations are effortless and others need care.
Authentication is handled through credentials, which store the keys or tokens that let n8n access an app on your behalf. You set these up once, securely, and every workflow can use them. Data flows through the workflow as structured items, so the output of one integration, say a list of contacts from your CRM, becomes the input the next node acts on. Between nodes, you map and transform that data so each app receives it in the shape it expects. Most integration work is exactly this: connecting accounts, then mapping data correctly from one system to the next. When it is done carefully, the workflow is reliable; when it is rushed, it breaks the first time the data looks slightly different from expected.
How to Set Up a New n8n Integration
Connecting a new app in n8n follows the same simple pattern regardless of the tool. First, you add the app’s node to your workflow, or the HTTP Request node if there is no dedicated one. Second, you create a credential: n8n walks you through connecting your account, usually by pasting an API key or signing in through the app, and stores it securely for reuse. Third, you configure the node to do what you want, choosing the action or trigger and mapping the data it should send or receive. Finally, you test it with real data before switching the workflow on.
For the 400-plus apps with native nodes, this takes minutes. For a service reached through the HTTP Request node, it takes a little more work: you tell n8n the API endpoint to call, how to authenticate, and what data to send, following the app’s API documentation. And for a custom or internal system, a developer may build a custom node so the integration is as clean and reusable as a native one. The pattern is always the same, connect, configure, map, and test, but the effort scales with how standard the integration is.
Popular n8n Integrations by Category
n8n integrations span almost every category of business software. The most commonly used tend to cluster in a handful of areas.
| Category | Examples of Apps You Can Connect |
| CRM and sales | HubSpot, Salesforce, Pipedrive, and other sales systems |
| Communication | Slack, Microsoft Teams, Gmail, Telegram, and messaging tools |
| Databases | Postgres, MySQL, MongoDB, Airtable, and Google Sheets |
| Marketing | Mailchimp, marketing platforms, ad tools, and analytics |
| Developer and DevOps | GitHub, GitLab, Jira, and CI and monitoring tools |
| AI and LLMs | OpenAI, Anthropic, and vector stores for AI workflows |
| Files and storage | Google Drive, Dropbox, S3, and document tools |
Marketing is one of the most active areas for n8n integrations, connecting the many tools a marketing team juggles into automated flows. For a real-world example, see How Automation with n8n Is Transforming Marketing Operations. The point is not any single integration but the combinations: the value appears when several apps are wired together into a process that runs itself.
A Practical Example
To see how integrations combine, imagine automating customer onboarding. When a new customer signs a contract in your e-signature tool, you want them created in your CRM, given access in your product, and welcomed by your team.
In n8n, a trigger node fires when the contract is signed. The next node creates the customer record in your CRM. A following node calls your product’s API, through a native node or the HTTP Request node, to provision their account. Another node adds them to your billing system. A final node posts a message in your team’s channel and sends the customer a personalised welcome email. Five integrations, one workflow, less time spent on routine tasks.
What used to be a checklist passed between three departments, with the delays and dropped steps that implies, becomes an instant, consistent process. This is the real power of n8n integrations: not connecting two apps, but orchestrating many into a process that runs itself. And because each integration is a discrete node, the workflow is easy to extend, for example by adding an AI step that tailors the welcome message to the customer’s industry.
Native Nodes vs. Community Nodes vs. Custom Integrations
Not every integration is equal, and knowing the four ways to connect an app to n8n helps set realistic expectations for any given tool.
| Method | What It Is | Best For |
| Native node | A built-in, officially maintained integration | The 400-plus popular apps n8n supports out of the box |
| Community node | An integration built by the community | Apps without an official node yet |
| HTTP Request node | A generic node that calls any REST API | Any service with an API but no ready node |
| Custom node | A purpose-built node you or a partner develops | Custom, internal, or legacy systems |
Native nodes, maintained officially, are the smoothest: well-tested, documented, and reliable. Community nodes, built by n8n’s large community, extend coverage to many more apps, though quality varies and they need vetting before production use. The HTTP Request node is the universal fallback: if a service has an API, n8n can talk to it, even without a dedicated node. And when a business runs custom, internal, or legacy systems, a custom node can be built to integrate them cleanly. Between these four, there is almost no system n8n cannot be connected to, given the right expertise.
Integrating n8n with Custom and Legacy Systems
The integrations that matter most to a business are often the ones no ready-made node covers: the in-house application, the industry-specific platform, the legacy system that has run operations for a decade. This is exactly where automation delivers the most value and where it gets technically demanding.
n8n can integrate with these systems through its HTTP Request node if they expose an API, through webhooks if they can send events, or through a purpose-built custom node for a clean, reusable connection. Doing this well is genuine software development: it requires understanding the system’s API or data model, handling authentication and errors properly, and building the integration to be maintainable. For businesses whose core systems are custom or older, this is where a partner who understands both n8n and application development turns a difficult integration into a reliable one. A well-built integration to a legacy system can unlock automation that was simply impossible before.
Connecting LLMs and AI Tools
One of the fastest-growing categories of n8n integration is AI. n8n connects natively to the major AI model providers and includes AI Agent nodes built on LangChain, the widely used framework for building applications with large language models. This lets a workflow do far more than move data: it can understand text, summarise documents, answer questions, classify requests, and make decisions.
These AI integrations connect not just to model providers but to the supporting pieces that make AI useful on your own data, such as vector stores for retrieval. That combination, an AI model plus your business data plus your other tools, is what turns automation into something genuinely intelligent, as explained in How RAG and Workflow Automation Power Digital Transformation. Building these integrations well is a specialism in itself, where a partner with real AI expertise makes the difference between a demo and a dependable system.
Do You Need a Developer to Build n8n Integrations?
Not always. n8n is designed so that connecting popular apps through native nodes is genuinely approachable, and a non-technical user can build useful integrations by following the visual interface. For straightforward connections between well-supported tools, in-house is perfectly reasonable and builds valuable capability.
Developer expertise becomes worthwhile as integrations get more demanding: connecting to a custom or legacy system with no ready node, building a custom node, handling complex authentication, integrating AI responsibly, or making an integration robust enough that the business can depend on it. At that point, the engineering behind the integration, the error handling, security, rate limits, and testing, matters as much as the connection itself. The sensible rule is to build the simple integrations yourself and bring in expertise for the ones that are technically hard or too important to break. Getting a critical integration wrong can quietly corrupt data across systems, which is far more expensive than building it properly the first time.
Building Reliable n8n Integrations: Common Challenges and Best Practices
An integration that works in a demo isn’t the same as one that holds up in production. Connecting real systems comes with a few recurring challenges, and each one has a practical way to handle it.
- Authentication and credentials: Some apps use simple API keys, while others require OAuth flows, token refreshes, or IP allowlisting. Since integrations hold the keys to your systems, set up authentication carefully and store and scope credentials securely, especially when self-hosting.
- Rate limits: Many APIs restrict how often you can call them and will start rejecting requests if you exceed that. Pace high-volume workflows so they stay within those limits.
- Data mapping: Matching the fields and formats one system expects with what another provides is fiddly and a common source of silent errors. Test with real data, including the messy edge cases a quick test usually misses.
- Unavailable apps and unexpected data: Services go down and responses don’t always look the way you expect. Build in error handling so the workflow can recover or alert someone instead of failing quietly.
- Breaking changes: When an app updates its API, an integration built for the old version can stop working without warning. Monitor your workflows and maintain them over time so problems are caught early.
- Missing or immature nodes: A community node may not cover everything you need. In that case, the HTTP Request node or a custom build can fill the gap.
None of these are reasons to avoid n8n. They’re simply part of connecting real systems, and they’re why integrations built with care last longer than ones put together quickly. Get them right, and your integrations become something your business can depend on. Skip them, and each one becomes a weak point that can quietly corrupt data or stop a critical process.
How Manao Builds n8n Integrations
Connecting two popular apps with a ready-made node is easy. Building integrations that are secure, reliable, and cover the custom and legacy systems that actually run a business is engineering work. Manao designs and builds n8n integrations across the full range, from simple connections to custom nodes for internal systems, backed by OMEGA, our proprietary AI-augmented delivery platform, and by senior engineers who understand both automation and the systems being connected.
The risk with integrations is the same as with any automation: anything can be wired together quickly, but a rushed integration breaks when an API changes, mishandles errors, or exposes data it should not. Manao builds integrations the way we build software, with proper authentication, error handling, testing, monitoring, and documentation, and with every AI-assisted step under experienced human review. There is no vibe coding, because an integration that fails silently is worse than no integration at all.
n8n Integration Services in Thailand: What Manao Software Delivers
Manao Software is a Danish-owned software development company operating across Chiang Mai and Bangkok, with over 19 years of experience building software, automation, and integrations for organisations across Europe, Australia, and Southeast Asia.
Our n8n integration work covers the full range a business needs: connecting the standard apps, integrating custom and legacy systems that lack a ready-made node, wiring in AI, and doing it all securely and reliably. What makes the Manao approach distinct:
- Custom integration expertise: we build the connections to internal and legacy systems that off-the-shelf nodes do not cover, including custom nodes
- Integrations built like software: proper authentication, error handling, testing, and monitoring, not fragile connections thrown together
- AI-capable: we connect n8n to AI models and your own data responsibly, with human oversight of every AI-assisted step
- Secure by design: credentials and data handled carefully, with self-hosting available so sensitive data stays under your control
- Full-time employees, not freelancers: every engineer on your engagement is a Manao full-time employee, with no continuity risk
Our philosophy, Straight Talk. Solid Delivery. applies to integrations the same way it applies to every engagement. Over 170 companies have trusted Manao Software to build software the right way. For more on choosing a partner in the region, see Choosing the Right Software Partner in Thailand.
n8n integrations are what turn an automation tool into a genuine operating layer for a business, connecting the apps, databases, custom systems, and AI models that the work actually runs on. The value is not in any single integration but in the ability to connect almost anything, reliably, into workflows that run themselves.
As software becomes ever more API-first and AI becomes part of everyday workflows, the businesses that benefit most are the ones that connect their systems well: securely, reliably, and including the custom and legacy pieces that generic tools ignore. Integration done properly is what separates automation that impresses in a demo from automation a business can depend on.
For businesses ready to connect their systems and automate the work between them, the right next step is a conversation about which integrations would deliver the most value and how to build them to last.
Ready to connect your systems with n8n?
Manao Software designs and builds n8n integrations for businesses that want reliable, secure connections across their apps, custom systems, and AI models, backed by over 19 years of engineering experience, OMEGA-powered delivery, and a team that builds integrations the way it builds software.
Talk to our team
