[{"data":1,"prerenderedAt":2326},["ShallowReactive",2],{"blog-\u002Fblog\u002F2024\u002F05\u002Funderstanding-node-flow-global-environment-variables-in-node-red":3,"featureCatalog":1396,"changelog-titles":1791,"blog-all-for-related":2325},{"id":4,"title":5,"authors":6,"body":8,"cta":1317,"date":1321,"description":1322,"extension":1323,"features":1324,"image":1325,"lastUpdated":1326,"meta":1327,"navigation":1384,"path":1385,"release":1324,"seo":1386,"sitemap":1387,"stem":1388,"subtitle":1389,"tags":1390,"tldr":1394,"video":1324,"__hash__":1395},"blog\u002Fblog\u002F2024\u002F05\u002Funderstanding-node-flow-global-environment-variables-in-node-red.md","How to Use Variables in Node-RED: Flow, Global, Context & Environment (2026)",[7],"sumit-shinde",{"type":9,"value":10,"toc":1295},"minimark",[11,67,70,75,78,81,97,103,109,113,116,122,127,133,136,149,158,161,245,251,254,261,264,328,334,341,345,348,354,358,363,366,373,375,433,438,441,448,450,510,516,523,527,530,536,540,543,548,610,615,680,686,690,693,696,700,705,708,713,716,824,829,832,839,841,951,954,958,961,968,973,991,994,1001,1005,1008,1011,1017,1023,1027,1032,1046,1053,1061,1066,1069,1076,1078,1140,1143,1174,1181,1191,1197,1201,1204,1209,1223,1239,1245,1251,1257,1263,1267,1285,1288,1291],[12,13,14,15,19,20,24,25,28,29,32,33,36,37,40,41,44,45,48,49,52,53,48,56,59,60,48,63,66],"p",{},"Node-RED has four types of variables: ",[16,17,18],"strong",{},"message variables"," that travel with ",[21,22,23],"code",{},"msg"," through your nodes, and ",[16,26,27],{},"context variables"," in three scopes, ",[16,30,31],{},"node"," (private to a single function node), ",[16,34,35],{},"flow"," (shared within one tab), and ",[16,38,39],{},"global"," (shared across the entire instance), plus ",[16,42,43],{},"environment variables"," for configuration and secrets. You set and retrieve context variables with ",[21,46,47],{},"global.set()","\u002F",[21,50,51],{},"global.get()",", ",[21,54,55],{},"flow.set()",[21,57,58],{},"flow.get()",", and ",[21,61,62],{},"context.set()",[21,64,65],{},"context.get()"," in function nodes, or visually through the change node. Context variables are stored in memory by default and are lost on restart, so any state that must survive a reboot needs persistent storage.",[12,68,69],{},"That's the short version. The rest of this guide walks through each variable type in detail, showing you exactly how to set, retrieve, and delete them, when to use each scope, and how to make them persist across restarts and redeployments.",[71,72,74],"h2",{"id":73},"what-are-node-red-variables","What Are Node-RED Variables?",[12,76,77],{},"Variables in Node-RED serve as containers for storing and managing data throughout your application. Understanding the different types and their scopes is essential for building efficient, organized flows.",[12,79,80],{},"Node-RED offers three primary variable categories:",[12,82,83,86,87,90,91,96],{},[16,84,85],{},"Message variables"," travel with the message object as it flows through your nodes. The most common example is ",[21,88,89],{},"msg.payload",", which carries the primary data between nodes. For a deeper dive into message handling, see the ",[92,93,95],"a",{"href":94},"\u002Fnode-red\u002Fgetting-started\u002Fnode-red-messages\u002F","Understanding Node-RED Messages"," guide.",[12,98,99,102],{},[16,100,101],{},"Context variables"," store application state at different levels, node, flow, or global scope. They persist data that needs to be accessed across multiple message events, making them ideal for tracking counters, storing configuration, or maintaining state.",[12,104,105,108],{},[16,106,107],{},"Environment variables"," handle configuration data and sensitive information like API keys and credentials. By storing this data separately from your flows, you maintain security and make configuration management more flexible.",[71,110,112],{"id":111},"global-variables-instance-wide-data-storage","Global Variables: Instance-Wide Data Storage",[12,114,115],{},"Global variables provide a centralized storage mechanism accessible throughout your entire Node-RED instance. Any function, change, inject, or switch node can read or write global variables, making them perfect for sharing data across multiple flows.",[12,117,118,121],{},[16,119,120],{},"When to use global variables:"," Consider using them for system-wide settings, shared configuration, or data that multiple flows need to access. For example, in a home automation system with separate flows for lighting, security, and climate control, global variables can store user preferences that all flows reference.",[123,124,126],"h3",{"id":125},"working-with-global-variables","Working with Global Variables",[12,128,129,132],{},[16,130,131],{},"Setting global variables"," can be done through the change node or programmatically in a function node:",[12,134,135],{},"Using the change node:",[137,138,139,143,146],"ol",{},[140,141,142],"li",{},"Select \"global\" from the variable type dropdown",[140,144,145],{},"Enter your variable name",[140,147,148],{},"Set the value or expression",[12,150,151],{},[152,153],"img",{"alt":154,"dataZoomable":155,"src":156,"title":157},"\"Screenshot showing how to set global variable using the change node\"","","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-setting-global-variable-using-change-node.png","Screenshot showing how to set global variable using the change node",[12,159,160],{},"Using a function node:",[162,163,167],"pre",{"className":164,"code":165,"language":166,"meta":155,"style":155},"language-javascript shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","global.set('userName', 'John');\nglobal.set('systemMode', 'active');\n","javascript",[21,168,169,214],{"__ignoreMap":155},[170,171,174,177,181,185,188,191,195,197,200,203,206,208,211],"span",{"class":172,"line":173},"line",1,[170,175,39],{"class":176},"sTEyZ",[170,178,180],{"class":179},"sMK4o",".",[170,182,184],{"class":183},"s2Zo4","set",[170,186,187],{"class":176},"(",[170,189,190],{"class":179},"'",[170,192,194],{"class":193},"sfazB","userName",[170,196,190],{"class":179},[170,198,199],{"class":179},",",[170,201,202],{"class":179}," '",[170,204,205],{"class":193},"John",[170,207,190],{"class":179},[170,209,210],{"class":176},")",[170,212,213],{"class":179},";\n",[170,215,217,219,221,223,225,227,230,232,234,236,239,241,243],{"class":172,"line":216},2,[170,218,39],{"class":176},[170,220,180],{"class":179},[170,222,184],{"class":183},[170,224,187],{"class":176},[170,226,190],{"class":179},[170,228,229],{"class":193},"systemMode",[170,231,190],{"class":179},[170,233,199],{"class":179},[170,235,202],{"class":179},[170,237,238],{"class":193},"active",[170,240,190],{"class":179},[170,242,210],{"class":176},[170,244,213],{"class":179},[12,246,247,250],{},[16,248,249],{},"Retrieving global variables"," follows a similar pattern:",[12,252,253],{},"In a change, inject, or switch node, simply set the action to “set”, choose the type as “global”, and specify the variable name.",[12,255,256],{},[152,257],{"alt":258,"dataZoomable":155,"src":259,"title":260},"\"Screenshot showing how to retrieve global variables using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-retrieving-global-variable-using-change-node.png","Screenshot showing how to retrieve global variables using the change node",[12,262,263],{},"In function nodes:",[162,265,267],{"className":164,"code":266,"language":166,"meta":155,"style":155},"const userName = global.get('userName');\nconst mode = global.get('systemMode');\n",[21,268,269,301],{"__ignoreMap":155},[170,270,271,275,278,281,284,286,289,291,293,295,297,299],{"class":172,"line":173},[170,272,274],{"class":273},"spNyl","const",[170,276,277],{"class":176}," userName ",[170,279,280],{"class":179},"=",[170,282,283],{"class":176}," global",[170,285,180],{"class":179},[170,287,288],{"class":183},"get",[170,290,187],{"class":176},[170,292,190],{"class":179},[170,294,194],{"class":193},[170,296,190],{"class":179},[170,298,210],{"class":176},[170,300,213],{"class":179},[170,302,303,305,308,310,312,314,316,318,320,322,324,326],{"class":172,"line":216},[170,304,274],{"class":273},[170,306,307],{"class":176}," mode ",[170,309,280],{"class":179},[170,311,283],{"class":176},[170,313,180],{"class":179},[170,315,288],{"class":183},[170,317,187],{"class":176},[170,319,190],{"class":179},[170,321,229],{"class":193},[170,323,190],{"class":179},[170,325,210],{"class":176},[170,327,213],{"class":179},[12,329,330,333],{},[16,331,332],{},"Deleting global variables"," can be accomplished through the change node by selecting \"delete\" from the action dropdown, or via the Context Data sidebar panel, which provides a comprehensive view of all variables.",[12,335,336],{},[152,337],{"alt":338,"dataZoomable":155,"src":339,"title":340},"\"Screenshot showing how to delete global variable using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-deleting-global-variable-using-change-node.png","Screenshot showing how to delete global variable using the change node",[71,342,344],{"id":343},"flow-variables-tab-scoped-data","Flow Variables: Tab-Scoped Data",[12,346,347],{},"Flow variables exist within a single tab or flow in your Node-RED editor. They're accessible to all nodes within that specific flow but isolated from other flows, providing logical data separation.",[12,349,350,353],{},[16,351,352],{},"When to use flow variables:"," Use them for data that's relevant only to a specific workflow. For instance, in a temperature monitoring flow with multiple sensor nodes, flow variables can track the current reading, alert thresholds, or calculation results, data that doesn't need to be shared with other parts of your application.",[123,355,357],{"id":356},"working-with-flow-variables","Working with Flow Variables",[12,359,360],{},[16,361,362],{},"Setting flow variables:",[12,364,365],{},"Using the change node, select the action “set”, choose “flow” as the variable type, and configure your variable.",[12,367,368],{},[152,369],{"alt":370,"dataZoomable":155,"src":371,"title":372},"\"Screenshot showing how to set flow variable using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-setting-flow-variable-using-change-node.png","Screenshot showing how to set flow variable using the change node",[12,374,263],{},[162,376,378],{"className":164,"code":377,"language":166,"meta":155,"style":155},"flow.set('currentTemp', 72.5);\nflow.set('alertThreshold', 85);\n",[21,379,380,407],{"__ignoreMap":155},[170,381,382,384,386,388,390,392,395,397,399,403,405],{"class":172,"line":173},[170,383,35],{"class":176},[170,385,180],{"class":179},[170,387,184],{"class":183},[170,389,187],{"class":176},[170,391,190],{"class":179},[170,393,394],{"class":193},"currentTemp",[170,396,190],{"class":179},[170,398,199],{"class":179},[170,400,402],{"class":401},"sbssI"," 72.5",[170,404,210],{"class":176},[170,406,213],{"class":179},[170,408,409,411,413,415,417,419,422,424,426,429,431],{"class":172,"line":216},[170,410,35],{"class":176},[170,412,180],{"class":179},[170,414,184],{"class":183},[170,416,187],{"class":176},[170,418,190],{"class":179},[170,420,421],{"class":193},"alertThreshold",[170,423,190],{"class":179},[170,425,199],{"class":179},[170,427,428],{"class":401}," 85",[170,430,210],{"class":176},[170,432,213],{"class":179},[12,434,435],{},[16,436,437],{},"Retrieving flow variables:",[12,439,440],{},"In a change, inject, or switch node, simply set the action to “set”, choose the type as “flow”, and specify the variable name.",[12,442,443],{},[152,444],{"alt":445,"dataZoomable":155,"src":446,"title":447},"\"Screenshot showing how to retrieve flow variable using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-retrieving-flow-variable-using-change-node.png","Screenshot showing how to retrieve flow variable using the change node",[12,449,263],{},[162,451,453],{"className":164,"code":452,"language":166,"meta":155,"style":155},"const temp = flow.get('currentTemp');\nconst threshold = flow.get('alertThreshold');\n",[21,454,455,483],{"__ignoreMap":155},[170,456,457,459,462,464,467,469,471,473,475,477,479,481],{"class":172,"line":173},[170,458,274],{"class":273},[170,460,461],{"class":176}," temp ",[170,463,280],{"class":179},[170,465,466],{"class":176}," flow",[170,468,180],{"class":179},[170,470,288],{"class":183},[170,472,187],{"class":176},[170,474,190],{"class":179},[170,476,394],{"class":193},[170,478,190],{"class":179},[170,480,210],{"class":176},[170,482,213],{"class":179},[170,484,485,487,490,492,494,496,498,500,502,504,506,508],{"class":172,"line":216},[170,486,274],{"class":273},[170,488,489],{"class":176}," threshold ",[170,491,280],{"class":179},[170,493,466],{"class":176},[170,495,180],{"class":179},[170,497,288],{"class":183},[170,499,187],{"class":176},[170,501,190],{"class":179},[170,503,421],{"class":193},[170,505,190],{"class":179},[170,507,210],{"class":176},[170,509,213],{"class":179},[12,511,512,515],{},[16,513,514],{},"Deleting flow variables"," works the same way as global variables, use the change node's delete action or the Context Data panel.",[12,517,518],{},[152,519],{"alt":520,"dataZoomable":155,"src":521,"title":522},"\"Screenshot showing how to delete flow variable using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-deleting-flow-variable-using-change-node.png","Screenshot showing how to delete flow variable using the change node",[71,524,526],{"id":525},"node-variables-node-level-isolation","Node Variables: Node-Level Isolation",[12,528,529],{},"Node variables (also called node context) are the most restrictive scope, they exist only within a single node. No other node can access or modify these variables, making them ideal for maintaining private state.",[12,531,532,535],{},[16,533,534],{},"When to use node variables:"," Perfect for counters, temporary calculations, or any data that should remain private to a specific node. For example, a function node that generates unique IDs for database records can maintain a counter variable that's never exposed to other parts of your flow.",[123,537,539],{"id":538},"working-with-node-variables","Working with Node Variables",[12,541,542],{},"Node variables are local to a Function node and cannot be read or modified by other nodes.",[12,544,545],{},[16,546,547],{},"Setting node variables:",[162,549,551],{"className":164,"code":550,"language":166,"meta":155,"style":155},"context.set('counter', 0);\ncontext.set('lastProcessedId', 'ABC123');\n",[21,552,553,580],{"__ignoreMap":155},[170,554,555,558,560,562,564,566,569,571,573,576,578],{"class":172,"line":173},[170,556,557],{"class":176},"context",[170,559,180],{"class":179},[170,561,184],{"class":183},[170,563,187],{"class":176},[170,565,190],{"class":179},[170,567,568],{"class":193},"counter",[170,570,190],{"class":179},[170,572,199],{"class":179},[170,574,575],{"class":401}," 0",[170,577,210],{"class":176},[170,579,213],{"class":179},[170,581,582,584,586,588,590,592,595,597,599,601,604,606,608],{"class":172,"line":216},[170,583,557],{"class":176},[170,585,180],{"class":179},[170,587,184],{"class":183},[170,589,187],{"class":176},[170,591,190],{"class":179},[170,593,594],{"class":193},"lastProcessedId",[170,596,190],{"class":179},[170,598,199],{"class":179},[170,600,202],{"class":179},[170,602,603],{"class":193},"ABC123",[170,605,190],{"class":179},[170,607,210],{"class":176},[170,609,213],{"class":179},[12,611,612],{},[16,613,614],{},"Retrieving node variables:",[162,616,618],{"className":164,"code":617,"language":166,"meta":155,"style":155},"let counter = context.get('counter');\ncounter++;\ncontext.set('counter', counter);\n",[21,619,620,649,656],{"__ignoreMap":155},[170,621,622,625,628,630,633,635,637,639,641,643,645,647],{"class":172,"line":173},[170,623,624],{"class":273},"let",[170,626,627],{"class":176}," counter ",[170,629,280],{"class":179},[170,631,632],{"class":176}," context",[170,634,180],{"class":179},[170,636,288],{"class":183},[170,638,187],{"class":176},[170,640,190],{"class":179},[170,642,568],{"class":193},[170,644,190],{"class":179},[170,646,210],{"class":176},[170,648,213],{"class":179},[170,650,651,653],{"class":172,"line":216},[170,652,568],{"class":176},[170,654,655],{"class":179},"++;\n",[170,657,659,661,663,665,667,669,671,673,675,678],{"class":172,"line":658},3,[170,660,557],{"class":176},[170,662,180],{"class":179},[170,664,184],{"class":183},[170,666,187],{"class":176},[170,668,190],{"class":179},[170,670,568],{"class":193},[170,672,190],{"class":179},[170,674,199],{"class":179},[170,676,677],{"class":176}," counter)",[170,679,213],{"class":179},[12,681,682,685],{},[16,683,684],{},"Deleting node variables"," must be done through the Context Data sidebar panel.",[71,687,689],{"id":688},"persistent-storage-with-flowfuse","Persistent Storage with FlowFuse",[12,691,692],{},"By default, all context variables (node, flow, and global) are stored in memory. This means they're lost whenever you restart Node-RED or redeploy your flows. For production applications, this is often unacceptable.",[12,694,695],{},"FlowFuse provides persistent storage that survives restarts, redeployments, and system updates. This ensures your application state remains intact across sessions.",[123,697,699],{"id":698},"using-persistent-storage","Using Persistent Storage",[12,701,702],{},[16,703,704],{},"Setting persistent variables:",[12,706,707],{},"In the change node, select \"persistent\" from the store dropdown instead of \"memory\".",[12,709,710],{},[152,711],{"alt":154,"dataZoomable":155,"src":712,"title":157},"\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-change-node-persistent-store-option-for-while-setting-variable.gif",[12,714,715],{},"In function nodes, add \"persistent\" as a third parameter:",[162,717,719],{"className":164,"code":718,"language":166,"meta":155,"style":155},"global.set('userData', userData, 'persistent');\nflow.set('sessionConfig', config, 'persistent');\ncontext.set('processedCount', count, 'persistent');\n",[21,720,721,756,790],{"__ignoreMap":155},[170,722,723,725,727,729,731,733,736,738,740,743,745,747,750,752,754],{"class":172,"line":173},[170,724,39],{"class":176},[170,726,180],{"class":179},[170,728,184],{"class":183},[170,730,187],{"class":176},[170,732,190],{"class":179},[170,734,735],{"class":193},"userData",[170,737,190],{"class":179},[170,739,199],{"class":179},[170,741,742],{"class":176}," userData",[170,744,199],{"class":179},[170,746,202],{"class":179},[170,748,749],{"class":193},"persistent",[170,751,190],{"class":179},[170,753,210],{"class":176},[170,755,213],{"class":179},[170,757,758,760,762,764,766,768,771,773,775,778,780,782,784,786,788],{"class":172,"line":216},[170,759,35],{"class":176},[170,761,180],{"class":179},[170,763,184],{"class":183},[170,765,187],{"class":176},[170,767,190],{"class":179},[170,769,770],{"class":193},"sessionConfig",[170,772,190],{"class":179},[170,774,199],{"class":179},[170,776,777],{"class":176}," config",[170,779,199],{"class":179},[170,781,202],{"class":179},[170,783,749],{"class":193},[170,785,190],{"class":179},[170,787,210],{"class":176},[170,789,213],{"class":179},[170,791,792,794,796,798,800,802,805,807,809,812,814,816,818,820,822],{"class":172,"line":658},[170,793,557],{"class":176},[170,795,180],{"class":179},[170,797,184],{"class":183},[170,799,187],{"class":176},[170,801,190],{"class":179},[170,803,804],{"class":193},"processedCount",[170,806,190],{"class":179},[170,808,199],{"class":179},[170,810,811],{"class":176}," count",[170,813,199],{"class":179},[170,815,202],{"class":179},[170,817,749],{"class":193},[170,819,190],{"class":179},[170,821,210],{"class":176},[170,823,213],{"class":179},[12,825,826],{},[16,827,828],{},"Retrieving persistent variables:",[12,830,831],{},"In a change, inject, or switch node, ensure you're selecting from the \"persistent\" store.",[12,833,834],{},[152,835],{"alt":836,"dataZoomable":155,"src":837,"title":838},"\"Screenshot showing how to retrieve global variable using the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-change-node-persistent-store-option.gif","Screenshot showing how to retrieve global variable using the change node",[12,840,263],{},[162,842,844],{"className":164,"code":843,"language":166,"meta":155,"style":155},"const userData = global.get('userData', 'persistent');\nconst config = flow.get('sessionConfig', 'persistent');\nconst count = context.get('processedCount', 'persistent');\n",[21,845,846,881,916],{"__ignoreMap":155},[170,847,848,850,853,855,857,859,861,863,865,867,869,871,873,875,877,879],{"class":172,"line":173},[170,849,274],{"class":273},[170,851,852],{"class":176}," userData ",[170,854,280],{"class":179},[170,856,283],{"class":176},[170,858,180],{"class":179},[170,860,288],{"class":183},[170,862,187],{"class":176},[170,864,190],{"class":179},[170,866,735],{"class":193},[170,868,190],{"class":179},[170,870,199],{"class":179},[170,872,202],{"class":179},[170,874,749],{"class":193},[170,876,190],{"class":179},[170,878,210],{"class":176},[170,880,213],{"class":179},[170,882,883,885,888,890,892,894,896,898,900,902,904,906,908,910,912,914],{"class":172,"line":216},[170,884,274],{"class":273},[170,886,887],{"class":176}," config ",[170,889,280],{"class":179},[170,891,466],{"class":176},[170,893,180],{"class":179},[170,895,288],{"class":183},[170,897,187],{"class":176},[170,899,190],{"class":179},[170,901,770],{"class":193},[170,903,190],{"class":179},[170,905,199],{"class":179},[170,907,202],{"class":179},[170,909,749],{"class":193},[170,911,190],{"class":179},[170,913,210],{"class":176},[170,915,213],{"class":179},[170,917,918,920,923,925,927,929,931,933,935,937,939,941,943,945,947,949],{"class":172,"line":658},[170,919,274],{"class":273},[170,921,922],{"class":176}," count ",[170,924,280],{"class":179},[170,926,632],{"class":176},[170,928,180],{"class":179},[170,930,288],{"class":183},[170,932,187],{"class":176},[170,934,190],{"class":179},[170,936,804],{"class":193},[170,938,190],{"class":179},[170,940,199],{"class":179},[170,942,202],{"class":179},[170,944,749],{"class":193},[170,946,190],{"class":179},[170,948,210],{"class":176},[170,950,213],{"class":179},[12,952,953],{},"Persistent storage allows Node-RED to retain state between restarts, crucial for historical metrics, long-running counters, dashboard application data, and any flow that must persist through a reboot without losing information.",[71,955,957],{"id":956},"the-context-data-panel","The Context Data Panel",[12,959,960],{},"Node-RED includes a dedicated Context Data panel in the sidebar that provides visibility into all your variables. This panel is invaluable for debugging and understanding your application's state.",[12,962,963],{},[152,964],{"alt":965,"dataZoomable":155,"src":966,"title":967},"\"Screenshot showing Node-RED Context data tab\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-context-data-tab.png","Screenshot showing Node-RED Context data tab",[12,969,970],{},[16,971,972],{},"Features of the Context Data panel:",[974,975,976,979,982,985,988],"ul",{},[140,977,978],{},"View all node, flow, and global variables in organized sections",[140,980,981],{},"See when each variable was last updated",[140,983,984],{},"Copy variable names or values with one click",[140,986,987],{},"Refresh individual variables to see current values",[140,989,990],{},"Delete variables directly from the interface",[12,992,993],{},"To access this panel, open the sidebar and choose ‘Context Data’ from the dropdown menu. Use the refresh icon in each section to update the display with the latest values.",[12,995,996],{},[152,997],{"alt":998,"dataZoomable":155,"src":999,"title":1000},"\"Screenshot showing Node-RED Context data tab options for managing variables\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-context-data-tab-options-for-varrables.png","Screenshot showing Node-RED Context data tab options for managing variables",[71,1002,1004],{"id":1003},"environment-variables-secure-configuration","Environment Variables: Secure Configuration",[12,1006,1007],{},"Environment variables serve a different purpose than context variables, they're designed for configuration data, especially sensitive information that shouldn't be hardcoded in your flows.",[12,1009,1010],{},"Node-RED supports environment variables at two levels:",[12,1012,1013,1016],{},[16,1014,1015],{},"Flow-level environment variables"," are accessible only within a specific flow. This is useful when different flows need different configurations. For example, one flow might connect to a development database while another connects to production, each using its own credentials.",[12,1018,1019,1022],{},[16,1020,1021],{},"Global-level environment variables"," are accessible across all flows in your instance. Use these for shared configuration like API keys that multiple flows need to reference.",[123,1024,1026],{"id":1025},"working-with-environment-variables","Working with Environment Variables",[12,1028,1029],{},[16,1030,1031],{},"Setting flow-level environment variables:",[137,1033,1034,1037,1040,1043],{},[140,1035,1036],{},"Double-click on the flow tab to open the edit dialog",[140,1038,1039],{},"Navigate to the \"Environment Variables\" section",[140,1041,1042],{},"Add your variables as name-value pairs",[140,1044,1045],{},"Click Done and deploy",[12,1047,1048],{},[152,1049],{"alt":1050,"dataZoomable":155,"src":1051,"title":1052},"\"Screenshot showing how to set flow level environment variables\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-setting-flow-scope-enviroment-variable.gif","Screenshot showing how to set flow level environment variables",[12,1054,1055,1056,1060],{},"For global-level environment variables, see ",[92,1057,1059],{"href":1058},"\u002Fblog\u002F2023\u002F01\u002Fenvironment-variables-in-node-red\u002F","Using Environment Variables in Node-RED"," for detailed instructions.",[12,1062,1063],{},[16,1064,1065],{},"Accessing environment variables:",[12,1067,1068],{},"In change, inject, or switch nodes, select \"env variable\" and specify the name.",[12,1070,1071],{},[152,1072],{"alt":1073,"dataZoomable":155,"src":1074,"title":1075},"\"Screenshot showing how to retrieve environment variable in the change node\"","\u002Fblog\u002F2024\u002F05\u002Fimages\u002Fvariables-in-node-red-retrieving-environment-variable-using-change-node.png","Screenshot showing how to retrieve environment variable in the change node",[12,1077,263],{},[162,1079,1081],{"className":164,"code":1080,"language":166,"meta":155,"style":155},"const apiKey = env.get('API_KEY');\nconst dbHost = env.get('DB_HOST');\n",[21,1082,1083,1112],{"__ignoreMap":155},[170,1084,1085,1087,1090,1092,1095,1097,1099,1101,1103,1106,1108,1110],{"class":172,"line":173},[170,1086,274],{"class":273},[170,1088,1089],{"class":176}," apiKey ",[170,1091,280],{"class":179},[170,1093,1094],{"class":176}," env",[170,1096,180],{"class":179},[170,1098,288],{"class":183},[170,1100,187],{"class":176},[170,1102,190],{"class":179},[170,1104,1105],{"class":193},"API_KEY",[170,1107,190],{"class":179},[170,1109,210],{"class":176},[170,1111,213],{"class":179},[170,1113,1114,1116,1119,1121,1123,1125,1127,1129,1131,1134,1136,1138],{"class":172,"line":216},[170,1115,274],{"class":273},[170,1117,1118],{"class":176}," dbHost ",[170,1120,280],{"class":179},[170,1122,1094],{"class":176},[170,1124,180],{"class":179},[170,1126,288],{"class":183},[170,1128,187],{"class":176},[170,1130,190],{"class":179},[170,1132,1133],{"class":193},"DB_HOST",[170,1135,190],{"class":179},[170,1137,210],{"class":176},[170,1139,213],{"class":179},[12,1141,1142],{},"In template nodes:",[162,1144,1146],{"className":164,"code":1145,"language":166,"meta":155,"style":155},"API Endpoint: {{env.API_ENDPOINT}}\n",[21,1147,1148],{"__ignoreMap":155},[170,1149,1150,1153,1157,1160,1163,1166,1168,1171],{"class":172,"line":173},[170,1151,1152],{"class":176},"API ",[170,1154,1156],{"class":1155},"sBMFI","Endpoint",[170,1158,1159],{"class":179},":",[170,1161,1162],{"class":179}," {{",[170,1164,1165],{"class":176},"env",[170,1167,180],{"class":179},[170,1169,1170],{"class":176},"API_ENDPOINT",[170,1172,1173],{"class":179},"}}\n",[12,1175,1176,1177,1180],{},"For configuration nodes that don't have explicit environment variable support, you can often use the syntax ",[21,1178,1179],{},"${VARIABLE_NAME}"," in input fields.",[12,1182,1183,1186,1187,1190],{},[16,1184,1185],{},"Important note on precedence:"," When a flow-level and global-level environment variable share the same name, Node-RED uses the flow-level value. To explicitly access the global-level variable, prefix it with ",[21,1188,1189],{},"$parent."," in your reference.",[12,1192,1193,1196],{},[16,1194,1195],{},"Deleting environment variables:"," Return to the flow edit dialog where you added them and click the delete icon next to each variable. Remember to redeploy your flows after making changes.",[71,1198,1200],{"id":1199},"best-practices","Best Practices",[12,1202,1203],{},"Here are some guidelines for effective variable usage in Node-RED:",[12,1205,1206],{},[16,1207,1208],{},"Choose the right scope:",[974,1210,1211,1214,1217,1220],{},[140,1212,1213],{},"Use node variables for node-specific data",[140,1215,1216],{},"Use flow variables for data shared within a single workflow",[140,1218,1219],{},"Use global variables for system-wide shared data",[140,1221,1222],{},"Use environment variables for configuration and secrets",[12,1224,1225,1228,1229,52,1232,52,1235,1238],{},[16,1226,1227],{},"Naming conventions matter:"," Use clear, descriptive names. Consider prefixing variables with their purpose (e.g., ",[21,1230,1231],{},"sensor_temperature",[21,1233,1234],{},"config_timeout",[21,1236,1237],{},"user_preferences",").",[12,1240,1241,1244],{},[16,1242,1243],{},"Leverage persistent storage:"," For production applications, identify which variables need to survive restarts and use persistent storage for those.",[12,1246,1247,1250],{},[16,1248,1249],{},"Keep sensitive data in environment variables:"," Never hardcode API keys, passwords, or other secrets directly in flows. Always use environment variables.",[12,1252,1253,1256],{},[16,1254,1255],{},"Document your variables:"," Use the description field in your nodes to explain what variables are being set or read, especially for complex flows that others might maintain.",[12,1258,1259,1262],{},[16,1260,1261],{},"Monitor the Context Data panel:"," Regularly check this panel during development to verify variables are being set correctly and to catch potential issues early.",[71,1264,1266],{"id":1265},"conclusion","Conclusion",[12,1268,1269,1270,1273,1274,1277,1278,1281,1282,1284],{},"Node-RED's four variable types give you a clear toolkit for managing data and state. Use ",[16,1271,1272],{},"node context"," for private, node-specific values, ",[16,1275,1276],{},"flow variables"," for data shared within a single tab, and ",[16,1279,1280],{},"global variables"," for anything multiple flows need to reach. Reach for ",[16,1283,43],{}," when you're handling configuration and secrets that shouldn't be hardcoded. Matching the scope to the job keeps your flows organized, predictable, and easy for others to maintain.",[12,1286,1287],{},"The one thing to keep front of mind: context variables live in memory by default, so they reset on every restart or redeploy. For anything your application genuinely depends on, counters, cached configuration, dashboard history, plan for persistent storage from the start rather than discovering the gap in production.",[12,1289,1290],{},"Get the scopes right and lean on persistence where it matters, and Node-RED will handle everything from quick prototypes to applications you can run with confidence.",[1292,1293,1294],"style",{},"html pre.shiki code .sTEyZ, html code.shiki .sTEyZ{--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html pre.shiki code .s2Zo4, html code.shiki .s2Zo4{--shiki-light:#6182B8;--shiki-default:#82AAFF;--shiki-dark:#82AAFF}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .spNyl, html code.shiki .spNyl{--shiki-light:#9C3EDA;--shiki-default:#C792EA;--shiki-dark:#C792EA}html pre.shiki code .sbssI, html code.shiki .sbssI{--shiki-light:#F76D47;--shiki-default:#F78C6C;--shiki-dark:#F78C6C}html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}",{"title":155,"searchDepth":1296,"depth":1296,"links":1297},4,[1298,1299,1302,1305,1308,1311,1312,1315,1316],{"id":73,"depth":216,"text":74},{"id":111,"depth":216,"text":112,"children":1300},[1301],{"id":125,"depth":658,"text":126},{"id":343,"depth":216,"text":344,"children":1303},[1304],{"id":356,"depth":658,"text":357},{"id":525,"depth":216,"text":526,"children":1306},[1307],{"id":538,"depth":658,"text":539},{"id":688,"depth":216,"text":689,"children":1309},[1310],{"id":698,"depth":658,"text":699},{"id":956,"depth":216,"text":957},{"id":1003,"depth":216,"text":1004,"children":1313},[1314],{"id":1025,"depth":658,"text":1026},{"id":1199,"depth":216,"text":1200},{"id":1265,"depth":216,"text":1266},{"type":1318,"title":1319,"description":1320},"signup","Take Your Node-RED Flows to Production with FlowFuse","Built by the team behind Node-RED, FlowFuse turns your flows into production-grade applications, with persistent state that survives restarts, centralized management of every instance, team collaboration with role-based access and SSO, DevOps pipelines, and built-in monitoring with crash alerts. Start your free trial today.","2024-05-06","Learn how to use Node-RED global, flow, context, and environment variables in 2026. Step-by-step examples for setting, retrieving, and persisting state, plus best practices and an FAQ.","md",null,"\u002Fblog\u002F2024\u002F05\u002Fimages\u002Funderstanding-node-red-variables.png","2026-06-01",{"keywords":1328,"faq":1329,"excerpt":1354},"node-red variables, node-red global variable, node-red context variable, node-red flow variable, node-red environment variables",[1330,1333,1336,1339,1342,1345,1348,1351],{"question":1331,"answer":1332},"What are the different types of variables in Node-RED?","Node-RED has three main categories: message variables (like msg.payload) that travel with the message through nodes; context variables that store state at node, flow, or global scope; and environment variables for configuration and secrets. Context variables are further split into node, flow, and global scopes based on visibility.",{"question":1334,"answer":1335},"What is the difference between flow and global variables in Node-RED?","Flow variables are scoped to a single tab and are accessible to all nodes within that flow but isolated from other flows. Global variables are accessible across your entire Node-RED instance, making them suited for system-wide settings or data multiple flows need to share.",{"question":1337,"answer":1338},"How do I set a global variable in a Node-RED function node?","Use global.set('variableName', value) to store a value and global.get('variableName') to retrieve it. The same pattern applies to flow variables (flow.set \u002F flow.get) and node context (context.set \u002F context.get).",{"question":1340,"answer":1341},"Do Node-RED variables persist after a restart?","By default, all context variables are stored in memory and are lost on restart or redeploy. To keep them, use persistent storage by adding 'persistent' as the store option in the change node or as a third parameter in a function node, e.g. global.set('userData', userData, 'persistent'). FlowFuse provides persistent storage that survives restarts and redeployments.",{"question":1343,"answer":1344},"What is the difference between context variables and environment variables?","Context variables (node, flow, global) store runtime application state that changes as your flows run. Environment variables hold configuration data and sensitive information like API keys and credentials, kept separate from your flows for security and easier configuration management.",{"question":1346,"answer":1347},"What happens if a flow-level and global-level environment variable have the same name?","Node-RED uses the flow-level value when names collide. To explicitly access the global-level variable instead, prefix the reference with $parent. in your variable name.",{"question":1349,"answer":1350},"When should I use node context instead of flow or global variables?","Use node context for private, node-specific data such as counters or temporary calculations that no other node should access. Node variables exist only within a single function node, providing the most restrictive and isolated scope.",{"question":1352,"answer":1353},"How can I view all the variables currently set in Node-RED?","Open the Context Data panel from the sidebar dropdown. It shows all node, flow, and global variables in organized sections, lets you see when each was last updated, copy names or values, refresh individual variables, and delete them directly from the interface.",{"type":9,"value":1355},[1356],[12,1357,14,1358,19,1360,24,1362,28,1364,32,1366,36,1368,40,1370,44,1372,48,1374,52,1376,48,1378,59,1380,48,1382,66],{},[16,1359,18],{},[21,1361,23],{},[16,1363,27],{},[16,1365,31],{},[16,1367,35],{},[16,1369,39],{},[16,1371,43],{},[21,1373,47],{},[21,1375,51],{},[21,1377,55],{},[21,1379,58],{},[21,1381,62],{},[21,1383,65],{},true,"\u002Fblog\u002F2024\u002F05\u002Funderstanding-node-flow-global-environment-variables-in-node-red",{"title":5,"description":1322},{"loc":1385},"blog\u002F2024\u002F05\u002Funderstanding-node-flow-global-environment-variables-in-node-red","A complete guide to setting, retrieving, and persisting Node-RED variables for efficient, production-ready flows.",[1391,1392,1393],"posts","node-red","how-to","Node-RED offers four kinds of variables for managing data and state: message variables that travel with msg through nodes, and context variables in three scopes node (private to one function node), flow (shared within a tab), and global (shared across the whole instance) plus environment variables for configuration and secrets. You set and retrieve them with global.set\u002Fget, flow.set\u002Fget, and context.set\u002Fget in function nodes, or visually through the change node. Context variables live in memory by default and are lost on restart, so use persistent storage (FlowFuse provides this) for any state that must survive reboots and redeployments.","c2oBECPVsWFsSJwOFynYJloGo50iINZ9YSx5U97rXC0",{"id":1397,"extension":1398,"meta":1399,"sections":1400,"stem":1789,"__hash__":1790},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[1401,1452,1553,1615,1692,1771],{"id":1402,"title":1403,"features":1404},"ai-automation","AI & Automation",[1405,1415,1425,1435,1441,1447],{"id":1406,"title":1407,"description":1408,"docsLink":1409,"changelog":1410,"tiers":1414},"flowfuse-expert-ai","FlowFuse Expert AI","Build industrial apps with agents, and query the state of the factory with an agent. Adapt your current hardware and machines so agentic work can be done against them, without ripping and replacing what's already on the plant floor.","\u002Fdocs\u002Fuser\u002Fexpert\u002F",[1411],{"url":1412,"release":1413},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":1384,"hub":1384,"fleet":1384},{"id":1416,"title":1417,"description":1418,"docsLink":1419,"changelog":1420,"subfeature":1384,"showOnPricing":1423,"tiers":1424},"flowfuse-expert-support-mode","Support Mode","Chat-based assistance for FlowFuse and Node-RED, including Node-RED instance management through natural language.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#support-mode",[1421],{"url":1422,"release":1413},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":1384,"hub":1384,"fleet":1384},{"id":1426,"title":1427,"description":1428,"docsLink":1429,"changelog":1430,"subfeature":1384,"showOnPricing":1423,"tiers":1434},"flowfuse-expert-application-building","Application Building","Describe what you want to build and FlowFuse Expert assembles it on your workspace, adding tabs, wiring nodes, and configuring properties.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F",[1431],{"url":1432,"release":1433},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":1384,"hub":1384,"fleet":1384},{"id":1436,"title":1437,"description":1438,"docsLink":1439,"subfeature":1384,"beta":1384,"showOnPricing":1423,"tiers":1440},"flowfuse-expert-insights-mode","Insights Mode","Connects FlowFuse Expert to MCP servers in your Node-RED instances, enabling real-time data queries and actions through a single chat interface.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#insights-mode",{"edge":1384,"hub":1384,"fleet":1384},{"id":1442,"title":1443,"description":1444,"docsLink":1445,"tiers":1446},"mcp-servers","Agentic Operations","Expose your Node-RED flows as tools an AI agent can call directly, so agents can query the state of the factory or trigger actions without custom integration work.","\u002Fnode-red\u002Fflowfuse\u002Fmcp\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1448,"title":1449,"description":1450,"tiers":1451},"onnx-integration","ONNX Integration","Run trained machine learning models directly in your flows, including on edge hardware, without sending data out to an external inference service.",{"edge":1384,"hub":1384,"fleet":1384},{"id":1453,"title":1454,"features":1455},"build","Build",[1456,1462,1468,1478,1484,1490,1494,1500,1506,1514,1520,1524,1528,1537,1545],{"id":1457,"title":1458,"description":1459,"docsLink":1460,"tiers":1461},"edge-development","Edge Development","Develop and test Node-RED flows directly on edge devices with a remote editor proxy.","\u002Fdocs\u002Fdevice-agent\u002Fquickstart\u002F",{"edge":1384,"hub":1423,"fleet":1384},{"id":1463,"title":1464,"description":1465,"docsLink":1466,"tiers":1467},"private-npm-registry","Custom Node-RED Nodes","Create and manage your own private npm registry for Node-RED nodes, so you can share custom nodes across your team and devices without publishing them publicly.","\u002Fdocs\u002Fuser\u002Fcustom-npm-packages\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1469,"title":1470,"description":1471,"docsLink":1472,"changelog":1473,"tiers":1477},"flowfuse-tables","FlowFuse Tables","A managed PostgreSQL database for every application, so you can store and query structured data without standing up and maintaining your own database.","\u002Fdocs\u002Fuser\u002Fff-tables\u002F",[1474],{"url":1475,"release":1476},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":1384,"hub":1384,"fleet":1384},{"id":1479,"title":1480,"description":1481,"docsLink":1482,"tiers":1483},"persistent-files","File Storage","Store and retrieve files from your Node-RED flows, with automatic replication and backup across your devices and hosted instances.","\u002Fdocs\u002Finstall\u002Ffile-storage\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1485,"title":1486,"description":1487,"docsLink":1488,"showOnPricing":1423,"tiers":1489},"persistent-context","Persistent Context","In-memory values defined in a Node-RED flow persist across project restarts and upgrades.","\u002Fdocs\u002Fuser\u002Fpersistent-context\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1491,"title":1492,"showOnPricing":1423,"tiers":1493},"static-assets","Static Assets",{"edge":1384,"hub":1384,"fleet":1384},{"id":1495,"title":1496,"description":1497,"docsLink":1498,"tiers":1499},"team-library","Team Library","Set up standard nodes and flows that can be shared with all team members across your organisation.","\u002Fdocs\u002Fuser\u002Fshared-library\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1501,"title":1502,"description":1503,"docsLink":1504,"tiers":1505},"personalised-multi-user-dashboards","Personalised Multi-User Dashboards","Build applications that provide unique data to each logged-in user using personalised multi-user dashboards.","https:\u002F\u002Fdashboard.flowfuse.com\u002Fuser\u002Fmulti-tenancy.html",{"edge":1384,"hub":1384,"fleet":1384},{"id":1507,"title":1508,"description":1509,"changelog":1510,"subfeature":1384,"showOnPricing":1423,"tiers":1513},"dashboards-view","Dashboards View","Browse and open every dashboard across your team from a dedicated Dashboards view, at both team and application level, without leaving FlowFuse.",[1511],{"url":1512,"release":1476},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1515,"title":1516,"description":1517,"docsLink":1518,"tiers":1519},"blueprints-converge","Blueprints","Ready-made starting points for your apps, from cross-team Converge templates to OT and IT specific blueprints.","\u002Fdocs\u002Fuser\u002Fconcepts\u002F#blueprint",{"edge":1384,"hub":1384,"fleet":1384},{"id":1521,"title":1522,"subfeature":1384,"showOnPricing":1423,"tiers":1523},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":1384,"hub":1423,"fleet":1384},{"id":1525,"title":1526,"subfeature":1384,"showOnPricing":1423,"tiers":1527},"blueprints-it-apps","Blueprints - IT APPS",{"edge":1423,"hub":1384,"fleet":1423},{"id":1529,"title":1530,"description":1531,"changelog":1532,"showOnPricing":1423,"tiers":1536},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[1533],{"url":1534,"release":1535},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":1384,"hub":1384,"fleet":1384},{"id":1538,"title":1539,"description":1540,"changelog":1541,"showOnPricing":1423,"tiers":1544},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[1542],{"url":1543,"release":1433},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1546,"title":1547,"description":1548,"changelog":1549,"showOnPricing":1423,"tiers":1552},"embedded-editor-tab-title","Embedded Editor Browser Tab Title","The browser tab title updates to reflect the active Node-RED canvas tab when working in the embedded editor.",[1550],{"url":1551,"release":1535},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1554,"title":1555,"features":1556},"deploy","Deploy",[1557,1563,1572,1578,1584,1590,1596,1602,1607],{"id":1558,"title":1559,"description":1560,"docsLink":1561,"tiers":1562},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":1384,"hub":1384,"fleet":1384},{"id":1564,"title":1565,"description":1566,"docsLink":1567,"changelog":1568,"tiers":1571},"edge-devices","Edge Instances","Deploy and mange your Node-RED instances on edge PLCs and gateways, with full visibility and control from the cloud.","\u002Fdocs\u002Fdevice-agent\u002Fintroduction\u002F",[1569],{"url":1570,"release":1413},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":1384,"hub":1423,"fleet":1384},{"id":1573,"title":1574,"description":1575,"docsLink":1576,"tiers":1577},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":1423,"hub":1384,"fleet":1423},{"id":1579,"title":1580,"description":1581,"docsLink":1582,"tiers":1583},"mqtt-broker","MQTT Broker","Manage and create MQTT clients to transport data for efficient messaging and communication within your applications.","\u002Fdocs\u002Fuser\u002Fteambroker\u002F",{"edge":1384,"hub":1423,"fleet":1384},{"id":1585,"title":1586,"description":1587,"docsLink":1588,"showOnPricing":1423,"tiers":1589},"project-nodes","Project Nodes aka seamless project comms","FlowFuse Project Nodes enable the passing of data and messages between your Node-RED projects.","\u002Fdocs\u002Fuser\u002Fprojectnodes\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1591,"title":1592,"description":1593,"docsLink":1594,"tiers":1595},"devops-pipelines","DevOps Pipelines","Set up different environments for development, testing, and production Node-RED instances to support a full software delivery lifecycle.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1597,"title":1598,"description":1599,"docsLink":1600,"tiers":1601},"git-integration","Git Integration","Back up your flows to a remote Git repository through a DevOps Pipeline. Supports GitHub and Azure DevOps repositories.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F#git-repository-stage",{"edge":1423,"hub":1384,"fleet":1423},{"id":1603,"title":1604,"description":1605,"docsLink":1600,"subfeature":1384,"showOnPricing":1423,"tiers":1606},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":1423,"hub":1384,"fleet":1423},{"id":1608,"title":1609,"description":1610,"docsLink":1600,"changelog":1611,"subfeature":1384,"showOnPricing":1423,"tiers":1614},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[1612],{"url":1613,"release":1535},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":1423,"hub":1384,"fleet":1423},{"id":1616,"title":1617,"features":1618},"operate-maintain","Operate & Maintain",[1619,1625,1631,1636,1644,1648,1652,1657,1663,1669,1674,1680,1684,1688],{"id":1620,"title":1621,"description":1622,"docsLink":1623,"tiers":1624},"snapshots","Snapshots & Version History","Automatic snapshots on remote devices and hosted instances, plus a full version history timeline so you can roll back to any prior state.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1626,"title":1627,"description":1628,"docsLink":1629,"subfeature":1384,"showOnPricing":1423,"tiers":1630},"auto-snapshot-remote","Auto Snapshot (Remote)","Automatically capture a snapshot every time a remote instance is deployed, so you always have a recoverable history of what was running on each device.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#auto-snapshots",{"edge":1384,"hub":1384,"fleet":1384},{"id":1632,"title":1633,"description":1634,"docsLink":1629,"subfeature":1384,"showOnPricing":1423,"tiers":1635},"auto-snapshot-hosted","Auto Snapshot (Hosted)","Automatically capture a snapshot every time a hosted instance is deployed, so you always have a recoverable history of what was running.",{"edge":1384,"hub":1384,"fleet":1384},{"id":1637,"title":1638,"description":1639,"changelog":1640,"subfeature":1384,"showOnPricing":1423,"tiers":1643},"snapshot-comparison","Snapshot Comparison","Compare two snapshots side-by-side with a navigable diff view. Step through every changed, added, or deleted node and see property and code diffs.",[1641],{"url":1642,"release":1535},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1645,"title":1646,"subfeature":1384,"showOnPricing":1423,"tiers":1647},"version-history-timeline","Version History Timeline",{"edge":1384,"hub":1384,"fleet":1384},{"id":1649,"title":1650,"tiers":1651},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":1384,"hub":1384,"fleet":1384},{"id":1653,"title":1654,"description":1655,"tiers":1656},"device-fleet-updates","Device Fleet Updates","Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes, securely without requiring full device access for your whole organisation.",{"edge":1384,"hub":1423,"fleet":1384},{"id":1658,"title":1659,"description":1660,"docsLink":1661,"tiers":1662},"device-group-management","Device Group Management","Logically group devices assigned to an application and integrate device groups into your DevOps Pipeline for coordinated fleet updates.","\u002Fdocs\u002Fuser\u002Fdevice-groups\u002F",{"edge":1384,"hub":1423,"fleet":1384},{"id":1664,"title":1665,"description":1666,"docsLink":1667,"tiers":1668},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":1423,"hub":1384,"fleet":1423},{"id":1670,"title":1671,"description":1672,"tiers":1673},"performance-monitoring","Performance Monitoring & Alerts","Track CPU, memory, and event loop performance across your instances and devices, with email alerts when something needs your attention.",{"edge":1384,"hub":1384,"fleet":1384},{"id":1675,"title":1676,"description":1677,"docsLink":1678,"subfeature":1384,"showOnPricing":1423,"tiers":1679},"instance-monitoring","Instance Monitoring","Enable alerts to be sent via email when your Node-RED instances encounter issues.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#alerts",{"edge":1384,"hub":1384,"fleet":1384},{"id":1681,"title":1682,"subfeature":1384,"showOnPricing":1423,"tiers":1683},"email-alerts","Email Alerts",{"edge":1384,"hub":1384,"fleet":1384},{"id":1685,"title":1686,"showOnPricing":1423,"tiers":1687},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":1384,"hub":1384,"fleet":1384},{"id":1689,"title":1690,"tiers":1691},"protected-instances","Protected Instances",{"edge":1423,"hub":1384,"fleet":1423},{"id":1693,"title":1694,"features":1695},"govern-secure","Govern and Secure",[1696,1705,1711,1717,1722,1728,1734,1740,1748,1754,1760,1766],{"id":1697,"title":1698,"description":1699,"docsLink":1700,"changelog":1701,"tiers":1704},"single-sign-on","Single Sign-On (SSO)","Configure FlowFuse to work with your own SSO provider, allowing users to access FlowFuse with a single set of login credentials.","\u002Fdocs\u002Fadmin\u002Fsso\u002F",[1702],{"url":1703,"release":1476},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1706,"title":1707,"description":1708,"docsLink":1709,"tiers":1710},"two-factor-authentication","Two-Factor Authentication","Two-factor authentication adds an extra layer of security to your FlowFuse account.","\u002Fdocs\u002Fuser\u002Fuser-settings\u002F#two-factor-authentication",{"edge":1384,"hub":1384,"fleet":1384},{"id":1712,"title":1713,"description":1714,"docsLink":1715,"tiers":1716},"certified-nodes-it","Certified Nodes - IT","IT certified node bundle includes: Redis, MQTT, HTTP Request, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server","\u002Fblog\u002F2025\u002F07\u002Fcertified-nodes-v2\u002F",{"edge":1423,"hub":1384,"fleet":1384},{"id":1718,"title":1719,"description":1720,"tiers":1721},"certified-nodes-ot","Certified OT Connections - OPC-UA, Modbus, etc.","OT certified node bundle includes: OPC-UA, Modbus TCP & RTU, RTSP, EtherNet\u002FIP, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server",{"edge":1384,"hub":1423,"fleet":1423},{"id":1723,"title":1724,"description":1725,"docsLink":1726,"tiers":1727},"audit-log","Audit Log","Keep track of everything going on in your Node-RED instances and FlowFuse. Audit Logs provide details on what actions have taken place, when they happened, and who did them.","\u002Fdocs\u002Fuser\u002Flogs\u002F#audit-log",{"edge":1384,"hub":1384,"fleet":1384},{"id":1729,"title":1730,"description":1731,"docsLink":1732,"tiers":1733},"role-based-access-control","Role-Based Access Control","Control who can do what at both the team and application level, from viewers to admins.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1735,"title":1736,"description":1737,"docsLink":1738,"subfeature":1384,"showOnPricing":1423,"tiers":1739},"application-level-rbac","Application-Level RBAC","Fine-grained access control per application, allowing team members to have different permission levels across different applications without requiring separate teams.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F#application-level-rbac",{"edge":1384,"hub":1384,"fleet":1384},{"id":1741,"title":1742,"description":1743,"changelog":1744,"subfeature":1384,"showOnPricing":1423,"tiers":1747},"scoped-personal-access-tokens","Scoped Personal Access Tokens","Restrict a Personal Access Token to specific teams, limit it to read-only operations, or control whether it carries admin privileges.",[1745],{"url":1746,"release":1476},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":1384,"hub":1384,"fleet":1384},{"id":1749,"title":1750,"description":1751,"docsLink":1752,"showOnPricing":1423,"tiers":1753},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":1384,"hub":1384,"fleet":1384},{"id":1755,"title":1756,"description":1757,"docsLink":1758,"showOnPricing":1423,"tiers":1759},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":1384,"hub":1384,"fleet":1384},{"id":1761,"title":1762,"description":1763,"docsLink":1764,"tiers":1765},"baa-for-hipaa","BAA for HIPAA","FlowFuse can sign a Business Associate Agreement to ensure proper safeguarding of protected health information handled on your behalf.","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.5\u002F",{"edge":1423,"hub":1384,"fleet":1423},{"id":1767,"title":1768,"description":1769,"tiers":1770},"sbom","Software Bill of Materials","A complete list of all software components used in your Node-RED instances and hosted applications, including version numbers and license information.",{"edge":1423,"hub":1384,"fleet":1423},{"id":1772,"title":1773,"features":1774},"support","Support",[1775,1780,1784],{"id":1776,"title":1777,"docsLink":1778,"tiers":1779},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":1384,"hub":1384,"fleet":1384},{"id":1781,"title":1782,"showOnPricing":1423,"tiers":1783},"live-chat-support","Live Chat Support",{"edge":1384,"hub":1384,"fleet":1384},{"id":1785,"title":1786,"docsLink":1787,"tiers":1788},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":1384,"hub":1384,"fleet":1384},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[1792,1795,1798,1801,1804,1807,1809,1812,1815,1818,1821,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1936,1939,1942,1945,1948,1951,1954,1957,1959,1962,1965,1968,1971,1974,1976,1979,1982,1985,1988,1991,1994,1997,2000,2003,2006,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2052,2055,2058,2061,2064,2067,2070,2073,2076,2079,2082,2085,2088,2091,2094,2097,2100,2103,2106,2108,2111,2114,2117,2120,2123,2126,2129,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2283,2286,2289,2292,2295,2298,2301,2304,2307,2310,2313,2316,2319,2322],{"path":1793,"title":1794},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":1796,"title":1797},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":1799,"title":1800},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":1802,"title":1803},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":1805,"title":1806},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":1808,"title":1516},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":1810,"title":1811},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":1813,"title":1814},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":1816,"title":1817},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":1819,"title":1820},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":1822,"title":1707},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":1824,"title":1825},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":1827,"title":1828},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":1830,"title":1831},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":1833,"title":1834},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":1836,"title":1837},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":1839,"title":1840},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":1842,"title":1843},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":1845,"title":1846},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":1848,"title":1849},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":1851,"title":1852},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":1854,"title":1855},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":1857,"title":1858},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":1860,"title":1861},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":1863,"title":1864},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":1866,"title":1867},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":1869,"title":1870},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":1872,"title":1873},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":1875,"title":1876},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":1878,"title":1879},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":1881,"title":1882},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":1884,"title":1885},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":1887,"title":1888},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":1890,"title":1891},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":1893,"title":1894},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":1896,"title":1897},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":1899,"title":1900},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":1902,"title":1903},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":1905,"title":1906},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":1908,"title":1909},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":1911,"title":1912},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":1914,"title":1915},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":1917,"title":1918},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1920,"title":1921},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1923,"title":1924},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1926,"title":1927},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1929,"title":1930},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1932,"title":1933},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1935,"title":1933},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1937,"title":1938},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1940,"title":1941},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1943,"title":1944},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1946,"title":1947},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1949,"title":1950},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1952,"title":1953},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1955,"title":1956},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1958,"title":1956},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1960,"title":1961},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1963,"title":1964},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1966,"title":1967},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1969,"title":1970},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1972,"title":1973},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1975,"title":1973},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1977,"title":1978},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1980,"title":1981},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1983,"title":1984},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1986,"title":1987},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1989,"title":1990},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1992,"title":1993},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1995,"title":1996},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1998,"title":1999},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":2001,"title":2002},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":2004,"title":2005},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":2007,"title":1646},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":2009,"title":2010},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":2012,"title":2013},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":2015,"title":2016},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":2018,"title":2019},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":2021,"title":2022},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":2024,"title":2025},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":2027,"title":2028},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":2030,"title":2031},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":2033,"title":2034},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":2036,"title":2037},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":2039,"title":2040},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":2042,"title":2043},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":2045,"title":2046},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":2048,"title":2049},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":2051,"title":1646},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":2053,"title":2054},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":2056,"title":2057},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":2059,"title":2060},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":2062,"title":2063},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":2065,"title":2066},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":2068,"title":2069},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":2071,"title":2072},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":2074,"title":2075},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":2077,"title":2078},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":2080,"title":2081},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":2083,"title":2084},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":2086,"title":2087},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":2089,"title":2090},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":2092,"title":2093},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":2095,"title":2096},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":2098,"title":2099},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":2101,"title":2102},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":2104,"title":2105},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":2107,"title":2105},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":2109,"title":2110},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":2112,"title":2113},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":2115,"title":2116},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":2118,"title":2119},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":2121,"title":2122},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":2124,"title":2125},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":2127,"title":2128},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":2130,"title":1470},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":2132,"title":2133},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":2135,"title":2136},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":2138,"title":2139},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":2141,"title":2142},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":2144,"title":2145},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":2147,"title":2148},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":2150,"title":2151},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":2153,"title":2154},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":2156,"title":2157},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":2159,"title":2160},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":2162,"title":2163},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":2165,"title":2166},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":2168,"title":2169},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":2171,"title":2172},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":2174,"title":2175},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":2177,"title":2178},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":2180,"title":2181},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":2183,"title":2184},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":2186,"title":2187},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":2189,"title":2190},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":2192,"title":2193},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":2195,"title":2196},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":2198,"title":2199},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":2201,"title":2202},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":2204,"title":2205},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":2207,"title":2208},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":2210,"title":2211},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":2213,"title":2214},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":2216,"title":2217},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":2219,"title":2220},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":2222,"title":2223},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":2225,"title":2226},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":2228,"title":2229},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":2231,"title":2232},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":2234,"title":2235},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":2237,"title":2238},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":2240,"title":2241},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":2243,"title":2244},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":2246,"title":2247},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":2249,"title":2250},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":2252,"title":2253},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":2255,"title":2256},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":2258,"title":2259},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":2261,"title":2262},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":2264,"title":2265},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":2267,"title":2268},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":2270,"title":2271},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":2273,"title":2274},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":2276,"title":2277},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":2279,"title":2280},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":2282,"title":1539},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":2284,"title":2285},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":2287,"title":2288},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":2290,"title":2291},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":2293,"title":2294},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":2296,"title":2297},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":2299,"title":2300},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":2302,"title":2303},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":2305,"title":2306},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":2308,"title":2309},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":2311,"title":2312},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":2314,"title":2315},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":2317,"title":2318},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":2320,"title":2321},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":2323,"title":2324},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105886235]