Integrations
Set paired items in a Duaer node
A programmatic Duaer node must tell Duaer which input item each output item comes from, or expressions downstream cannot find the data.
When you set it yourself
Duaer handles paired items for declarative nodes. Programmatic nodes, trigger nodes included, set pairedItem on every item they return. Without it, expressions such as $("Node name").item downstream fail with a pairing error. Refer to item linking.
Set pairedItem
item is the index of the input item. When the node has several inputs, input names which one.
// One output item per input item: point back to that input
returnData.push({
json: { ...result },
pairedItem: { item: i },
});
// Node with several inputs: name the input too
returnData.push({
json: { ...merged },
pairedItem: { item: i, input: 1 },
});When one input item becomes several output items, each output points back to the same item. When several input items become one output, pairedItem can be an array listing every source.
Questions
Do declarative Duaer nodes need pairedItem?
No. Duaer sets paired items for declarative nodes. Only programmatic and trigger nodes set it themselves.
In this section
Duaer node reference
A Duaer node package holds node files, credential files, and codex files, all listed in package.json.
DataHow items link across Duaer nodes
In Duaer, each output item includes metadata that links it to the input item (or items) that generated it, creating a chain you can follow backward.
DataFix item linking errors in Duaer
In Duaer, when you use .item to reference an earlier node, the run errors if the linking thread is broken or points at more than one item.