n8n error

Fix “Paired item data … is unavailable” in n8n

⚠️ Paired item data for item from node is unavailable

What this error means

With .item, n8n follows each item back through the workflow to find the matching item in an earlier node (item linking). Some nodes create brand-new items without recording where they came from, so n8n can't tell which earlier item belongs to the current one.

Common causes

  • A Code node returns new items it built from scratch.
  • Aggregate, Summarize or Merge combined several items into one.
  • A community or HTTP-based step created new items without linking information.

How to fix it

  1. If the earlier node has only one item, use $('Node').first().json.field instead of .item.
  2. Carry the field forward: add it to the items with an Edit Fields node before the step that breaks the link, then read $json.field later.
  3. In a Code node that creates items, copy the fields you need from the input item into the new item.
  4. Use $('Node').all()[index] only when you are sure both lists are in the same order.

❌ Breaks

// After an Aggregate node
{{ $('Webhook').item.json.body.email }}

✅ Works

// Webhook received one item, so read the first
{{ $('Webhook').first().json.body.email }}

💡 Pro tip: Carrying fields forward is the most robust fix: the data travels with the item, so no lookup is needed later.

📖 n8n $('Node Name') reference →

Was this page helpful?

Practice the skill behind this fix

More n8n errors