Organizations and data

Edit the data in a node output

You can change a node output in the JSON view. After you save, the edited data is pinned on the node, and later steps in the editor read that version.

When to edit a node output

The real output is missing a field, or you want the next step to walk through a specific edge case. Editing this output is faster than changing the previous step and running it again. You are editing the editor copy, not a past execution stored in history.

Edit a node output in the JSON view and save

Open the node and switch the output to the JSON view. The table view is for reading. It does not edit fields.
Select Edit.
Change the items in place. Each item still needs json. Do not hand-write files into binary. Pinned data does not keep files.
Select Save. Saving also pins the data. The next manual run in the editor uses the edited copy until you Unpin.

Keep the shape later steps expect

If the next step reads {{ $json.customerId }}, renaming or deleting that key makes the expression empty. Keep nested objects at the same depth, so address.city is still inside address.

The number of items also changes what happens next. Three items edited down to one means a later per-item node runs once. Linking is covered in How items stay linked through a run.

[
  {
    "json": {
      "customerId": "c-18",
      "status": "past_due"
    }
  }
]

Questions

What happens when you save an edited node output in Duaer?

In Duaer, edit a node output from the JSON view with Edit. Save pins the edited data on that node. Later manual runs in the editor then read that edited copy until you Unpin. Saving does not change an execution already stored in history.

What shape must an edited Duaer node output keep?

An edited Duaer node output still needs json on every item. Keep the field names and nesting that later expressions read, so address.city stays inside address. Changing how many items there are changes how many times a later per-item node runs.

In this section

Data