Analytics preference

We only load Google Analytics after you opt in. You can change this choice at any time from Cookie settings.

Enable Node

The Enable Node node turns another node back on. When executed, it sets the target node's active to true and persists the change.

The Enable Node node turns another node back on. When executed, it sets the target node's active to true and persists the change. It is the counterpart of Disable Node: use it to re-arm a Cron trigger or any node that was switched off.

Overview

PropertyValue
Inputs1
Outputs1
Output$nodeLabel.targetNode, $nodeLabel.enabled

Parameters

ParameterTypeDescription
labelstringNode identifier (camelCase)
targetNodeLabelstringLabel of the node to enable (e.g. hourlyCheck)

Behavior

  • The target is saved as active, so future runs and triggers see it. A re-enabled Cron trigger fires again at its next scheduled time.
  • If the target sits downstream of the Enable Node and has not run yet, it also runs in the current execution.
  • Enabling a node that is already active changes nothing; the output still reports enabled: true.
  • The node fails with an error when targetNodeLabel is empty or no node has that label.

Use Case

Start a Cron trigger on demand. Save the Cron node switched off, and give the workflow a second entry point such as an Input trigger. A request to that entry point runs the Enable Node, and the Cron starts firing.

A switched-off trigger never starts a run by itself, so the Enable Node must sit behind an entry point that can run.

Example

{
  "type": "enableNode",
  "data": {
    "label": "startCron",
    "targetNodeLabel": "hourlyCheck"
  }
}

Flow: Input → Enable Node (target: cron) → Output. The Cron node hourlyCheck is saved as disabled in the same workflow and runs its own HTTP check branch once enabled.