Set Data

​

When to use this node

• Give several upstream values a stable object shape before passing them on.
• Create a small request body or notification payload without writing code.

​

Example: Build a normalized incident object

{
  "values": {
    "service": "checkout",
    "status": "{{nodes.request.output.status}}",
    "urgent": true
  }
}

1. Add the desired keys in values.
2. Map changing fields from earlier outputs.
3. Map the value output into an HTTP, AI, or Code node.

​

Configuration

​

Workflow JSON

{
  "type": "set_data",
  "version": 1,
  "configuration": {
    "values": {
      "key": "value"
    }
  }
}

​

Inputs

​

Outputs

​

Execution behavior

• The output is the resolved object; nested JSON-compatible values are preserved.
• Set Data transforms execution data only and does not persist workflow state between runs.
• The editor catalogue declares value (object) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​

Common issues

• Use Set Workflow State if the value must survive the current execution.
• Do not put secrets in a literal object; use protected values or connections at the consuming node.

​

Where it can run

• Desktop local runner
• Paired self-hosted runner
• Hosted runner

​

Test and inspect

​

Related guides

• Variables and data mapping
• JSON data