Renaming and Removing Message Fields in Node‑RED with the Change Node
Learn how to rename, add, or remove fields in Node‑RED messages using the Change node — no JavaScript required.
Loading…
ReadMeFeed / Community knowledge
#node-red
Real questions. Useful conversations. Find the people who know your stack.
noderedManaging State in Node-RED Using the Context API
Learn how to use Node-RED's Context API to maintain state across flows, implement persistent storage, and avoid common memory pitfalls in your automation logic.
Managing State in Node-RED: When to Use Node, Flow, and Global Context
Stop losing data between nodes. Learn how to use Node, Flow, and Global context in Node-RED to manage state, implement toggle logic, and ensure data persists across restarts.
Managing State in Node-RED: Choosing Between Node, Flow, and Global Context
Stop losing data between triggers. Learn how to use Node, Flow, and Global context in Node-RED to manage state and persist data across restarts.
Expose a Current‑Time REST Endpoint in Node‑RED: A Step‑by‑Step Guide
Learn how to create a lightweight REST API in Node‑RED that returns the server’s current time in JSON. Follow the prerequisites, wiring steps, verification commands, and troubleshooting tips to get a reliable /time endpoint.
jsonDoes Node-RED automatically clear global context variables during a flow deployment?
When developing flows that rely on global context for sharing state between nodes, it is important to know whether Node-RED resets this store each time a flow is deployed. The documentation states that global context variables persist across deployments unless they are explicitly cleared, but it does not specify whether a runtime option exists to automate th
Node-RED split node lacks back-pressure for large paginated API datasets
When a Node-RED flow uses the core split node to consume a large dataset returned by an external API, the runtime forwards each array element as fast as the Node.js event loop permits. There is no built-in back-pressure or bounded queue, so if a downstream HTTP request or database write is slower than the source, in-flight messages accumulate in memory. Pagi
credentialSecret compatibility boundary: restoring Node-RED flows without the original secret
Assuming a recent Node-RED runtime, migrating an instance between environments or restoring from backup may leave flows containing encrypted credentials generated under a different credentialSecret. The runtime does not validate during restore whether those encrypted values can be decrypted with the currently configured secret, so credential nodes appear pre
Node-RED Global Context and Node.js Heap Memory Integration
Memory Management in Global Context Node-RED utilizes the Node.js runtime, where the global context API provides a mechanism for sharing data across different flows. By default, this context is stored in memory, meaning any objects or arrays assigned to the global scope reside directly on the Node.js heap. While the runtime handles standard garbage collectio
nodejs