Node-RED

• Flows deployedRuns when someone deploys changes in Node-RED, saying which flows were added, changed, enabled, disabled or deleted: for a changelog, or to back the flows up after each change. Two deploys between looks are one run.

• Call flow endpointSend a request to a flow's own HTTP endpoint (an http in node) and get its answer, so a workflow can use logic built in Node-RED. Fails when the flow answers with an error status.
• Trigger inject nodeRun a flow from one of its inject nodes, as clicking its button in the editor does, with its own payload or one you give.
• Get context valueRead a value a flow keeps in Node-RED's context, such as a sensor reading or a counter, from global context or one flow's.
• List flowsList Node-RED's flows (the editor's tabs), with how many nodes each has, its HTTP endpoints and whether it's enabled; optionally with every flow exported as JSON, for a backup.
• Get flowGet one flow with its nodes, and its export as JSON: keep it as a backup, or add it to another Node-RED with Add flow.
• Add flowAdd a flow to Node-RED from its export (Export in Node-RED's menu, or Get flow's) and deploy it, as a new tab with new node IDs.
• Enable flowSwitch a disabled flow back on and deploy it, as the Disabled button in the flow's properties in the editor does.
• Disable flowSwitch a flow off and deploy it, so its nodes stop running until it's enabled again.
• Delete flowDelete a flow and its nodes from Node-RED and deploy. Nothing is deleted when it isn't there.
• Restart flowsStop and start every flow, as Node-RED's Deploy > Restart Flows does, such as after a device reconnects.
• Get server infoGet Node-RED's version, the Node.js it runs on, its memory use and the node modules installed, such as for a weekly check.

No actions match that.