n8n or Node-RED: which tool for which purpose

n8n is designed for business automation: SaaS integrations, APIs, structured workflows, and increasingly AI agents too. Node-RED is built for real-time events on hardware: IoT sensors, industrial protocols, Raspberry Pi projects. Both are open-source tools with a visual, node-based interface, but they solve different problems, and the choice depends on whether a cloud service or a piece of hardware is ultimately being addressed. For most office processes in German SMEs, n8n is the obvious choice; for building technology, machine connectivity, or sensor data, it's Node-RED. As of: August 2026.

What is n8n built for?

According to its own positioning, n8n targets technical teams who want to build API-driven business processes and AI automation, with a focus on data sovereignty and structured JSON logic (n8n.io, comparison page). According to the vendor, the tool comes with over 1,000 native integrations, plus unlimited REST and GraphQL connectivity as well as built-in AI infrastructure such as LLM and vector store integrations. For enterprise use, n8n offers role-based permissions, single sign-on, and audit logs, and for high load peaks, execution can be scaled horizontally via a Redis-backed queue mode. Individual building blocks such as the Webhook node also reflect this business focus: it supports the common HTTP methods, separates test from production URLs, and offers four response modes, up to and including streaming (docs.n8n.io, webhook node).

What is Node-RED built for?

Node-RED is a flow-based programming tool created in 2013 by Nick O'Leary and Dave Conway-Jones as part of IBM's Emerging Technology team, originally to visualize MQTT topics, and released as open source in September 2013. Today it is maintained by the OpenJS Foundation (nodered.org, about Node-RED). The combination of a browser-based editor and a lightweight Node.js runtime core makes it particularly attractive for resource-constrained hardware such as the Raspberry Pi, for IoT device integration, and for industrial applications that connect and transform operational data. Over 5,000 community-maintained nodes cover many industrial protocols, and the license under Apache 2.0 is completely free to use.

Where are the technical differences?

The key difference isn't in the look, but in the target environment: n8n orchestrates cloud workflows between accounting, CRM, and mail systems and is designed for structured, often asynchronous business logic. Node-RED controls sensors, actuators, and message buses in real time and stays closer to the hardware. In practice, this shows up in API connectivity: while n8n comes with dedicated nodes for many services, Node-RED's generic HTTP node can also connect to almost anything, but usually with more manual configuration. Conversely, n8n has no comparable visualization library to Node-RED's dashboard, which displays live data directly in the browser.

When does combining both tools make sense?

For many businesses, it's not an either-or but a side-by-side approach: Node-RED handles the on-site connectivity, for example to sensors or controllers, and n8n handles the subsequent business logic in the cloud, for example notifications, bookings, or reports. Anyone unsure which tool fits their use case should first check whether a SaaS service or a physical device is ultimately being addressed. For mixed requirements, a brief inventory of existing systems is worthwhile before building an automation. NordFlux supports this assessment as part of its n8n consulting and, if needed, also handles the technical implementation.

Frequently asked questions about n8n and Node-RED

Can Node-RED also connect to SaaS services like n8n?

Yes, the generic HTTP node can address almost any API, though without the dedicated integrations and structured error handling that n8n provides for many business services. For individual requests, this is often sufficient; for more complex business logic, the manual effort quickly grows.

Is n8n unsuitable for IoT projects?

n8n can process MQTT and webhook messages and is therefore suitable for simple event chains, but it is not designed for resource-constrained hardware or real-time requirements. For sensor data directly on the device or industrial protocols, Node-RED is the technically more fitting choice.

What does using Node-RED cost compared to n8n?

Node-RED is completely free under Apache 2.0, while n8n offers a free self-hosted option as well as paid cloud and enterprise tiers with additional features such as role-based permissions or single sign-on. Which option makes sense depends on the scope of the planned automation.

Can workflows be exchanged between n8n and Node-RED?

No, both tools store workflows in their own, incompatible JSON formats. In practice, a migration means rebuilding the logic in the target system, even if individual steps can be transferred conceptually one-to-one.