It´s not possible to connect OpenAI Node to a previous node

Questions
,
1

Does someone also encounter the aboved mentioned issue?

Describe the problem/error/question

What is the error message (if any)?

No path back to referenced node

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
    2.2.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud / via Integration
  • Operating system: Mac
2

Hi @IntriguedbyN8N

It means that the OpenAI node is using an expression that references another node, but there is no execution path (no wired connection) from the OpenAI node back to that referenced node.

n8n requires that any node you reference with expressions like $('Some Node').item is upstream in the same execution chain . If there’s no path, you get this error. [Item linking errors]

To troubleshoot:

  1. Check expressions in the OpenAI node
    Look for any expression referencing another node for example or similar. That referenced node must be connected upstream.

{{ $('Previous Node').item.json.someField }}

  1. Ensure there is a wired path
    Make sure the node you reference is connected (directly or via other nodes) to the OpenAI node’s input. If it’s on a different branch or not connected at all, n8n can’t build the “path back”.

  2. If wiring looks correct, try re‑creating the node
    As in the forum example, sometimes the internal link metadata can get into a bad state. Delete the OpenAI node (or the node mentioned in the error), add it again, reconnect, and re‑enter the expressions. [No path back bug]

If after that you still see the error, its likelly a general item-linking/wiring issue rather than a bug unique to the open AI.

Reference post: [SOLVED] Not path back to referenced node - Questions - n8n Community

3

@IntriguedbyN8N Welcome
Giving us more information about the scenario and workflow and your exact problem would help us narrow down the issue for you.