Node-RED is a free, open-source tool for wiring together automations visually — you connect nodes on a canvas to build flows that react to events, move data between services, and control devices, with little or no code. It started in the home-automation and Internet-of-Things world but is just as useful for business automation: glue between APIs, scheduled jobs, webhook processing, notifications. This guide explains what Node-RED is good for and how to deploy it as a one-click Docker container.
Automation you can see
Most automation lives in scripts — invisible until they break. Node-RED makes automation a diagram: each step is a node, wires connect them, and data flows left to right across the canvas. You drag an "inject" or a trigger node, connect it to a "function" or an HTTP-request node, connect that to an output, and deploy. The flow runs, and you can watch data move through it. For anyone who has inherited a pile of undocumented cron scripts, the visible-flow model is a relief.
What people build with it:
- Home and IoT automation — react to sensors, control smart devices, schedule actions. This is Node-RED's home turf, with a huge library of community nodes for devices and protocols.
- API glue — pull from one service on a schedule, transform the data, push it to another. The integration work that would otherwise be a fragile script.
- Webhook processing — receive a webhook, do something with it, respond. Node-RED can expose HTTP endpoints as flow entry points.
- Notifications and alerts — watch a condition, send a message to chat, email, or a phone.
If your automation needs are more about business workflows and SaaS connectors than devices, also look at n8n — we covered self-hosting n8n separately. Node-RED leans toward events, IoT, and lightweight glue; n8n leans toward business-app integrations. Many people run both.
Deploying Node-RED on Panelica
- Deploy the Node-RED template from the Docker app catalog. It is a single container.
- Note the data volume. Your flows, settings, and installed community nodes live in Node-RED's data directory — that volume is your entire automation setup, so it is what you protect.
- It is lightweight. Node-RED runs comfortably on modest resources, which is part of why it is popular on small home-lab servers.
- Open the editor on the published port — the flow canvas is the whole interface — and build your first flow.
Secure it before you build anything important
This is the one thing not to skip. By default a fresh Node-RED editor may be open to whoever can reach it — and the editor can run code and make network requests, so an open editor on the internet is a serious exposure. Two protections, both worth doing:
- Enable authentication in Node-RED's settings so the editor requires a login.
- Put it behind HTTPS and, ideally, restricted access. Link a subdomain like
automation.example.comthrough Panelica's reverse proxy for TLS, and if the editor is just for you, restrict the domain to your own IP.
An unsecured Node-RED editor is remote code execution waiting to happen. The editor is designed to run functions and reach out to networks — that power is the point, and exactly why you must not leave it open. Enable authentication before you expose it anywhere.
Flows that survive a rebuild
Your flows are the work. They live in the data volume, so backing that volume up means your automations survive a container rebuild or a server move. Export critical flows as JSON too — Node-RED lets you export and import flows as plain JSON, which is a convenient second copy and a way to version-control your automations.
Frequently asked questions
Do I need to know how to code?
For many flows, no — wiring nodes together covers a lot. When you need custom logic, the function node accepts JavaScript, so coding is available but not required. It scales with your comfort level.
Can it talk to my smart-home devices?
That is a core strength. Node-RED has a large ecosystem of community nodes for home-automation platforms, protocols, and devices, installable from within the editor.
What happens to a running flow if the container restarts?
Flows are restored from the data volume and resume. Anything held only in memory mid-execution is lost on restart, so design long-running or critical flows to be restartable — the same discipline as any service.
How do I move my setup to another server?
Copy the data volume, or export your flows as JSON and import them on the new instance. Because the whole configuration is in that volume, migration is mostly a volume-copy operation.
The takeaway
Node-RED turns automation into something you can see and wire together — ideal for IoT, event-driven glue, webhooks, and notifications, on a footprint small enough for any server. On Panelica it is a one-click container. The non-negotiable step is security: enable authentication and put it behind HTTPS before exposing it, because the editor can run code. Back up the data volume, keep JSON exports of your important flows, and you have a resilient automation hub you fully control.