n8n-MCP: complex Claude Desktop workflows won't open in n8n UI — 'propertyValues is not iterable'?

6 answers

• Best answerAgentArmorHQ teamTeam4d ago

  The issue is closed, but the thread does not mention an official fix or a patched version. The closest explanation offered is a user's hypothesis that the failure comes from the n8n Switch Node v2 bug, not from n8n-MCP itself.

  The only workaround reported to work: use the MCP tools for reading/inspecting workflows, but create the actual workflows through direct n8n API calls using Switch Node v3 instead of v2. The reporter said this same failure appeared with most MCP-generated workflows and that switching to v3 was their only working solution.

  For debugging, the maintainer asked for the failing workflow JSON and explained how to get it: open the broken workflow in the n8n editor, open the browser DevTools Network tab, and read the workflow JSON from a request response. The maintainer said they had hit this bug themselves and that the JSON is extractable this way, which is what the project needs to reproduce the issue.

  Notes from other reporters:

  • Some users see Could not find property option instead of propertyValues[itemName] is not iterable.
  • The error is not limited to complex workflows: one reporter hit Could not find property option even on a 2-node workflow.
  • Another user reported the workflow does not load at all — just an empty canvas.

  Reported environment: Windows 11, Claude Desktop, n8n 1.103.2, n8n-MCP 2.7.21 (GitHub latest, linked globally with npm link).

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @saul-revenue-diy tried on GitHub (Worked)

  Suspecting the n8n Switch Node v2 bug, the reporter used MCP only for reading workflows and built the actual workflows via direct n8n API calls using Switch Node v3. They reported this as their only working solution.

  Source: https://github.com/czlonkowski/n8n-mcp/issues/90#issuecomment-3117822909 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  After upgrading to n8n 1.103.2 and n8n-MCP 2.7.21, deployed a complex workflow via Claude Desktop MCP. It appeared in the n8n UI list but failed to open with a blank URL and the error Could not find workflow / propertyValues[itemName] is not iterable.

  Source: https://github.com/czlonkowski/n8n-mcp/issues/90 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @anis200 tried on GitHub (Didn't work)

  Another user reproduced the failure with a tiny 2-node workflow, seeing Could not find property option, so the problem is not specific to large or complex workflows.

  Source: https://github.com/czlonkowski/n8n-mcp/issues/90#issuecomment-3124272302 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @jonathanlaniado tried on GitHub (Didn't work)

  One user reported the workflow does not load at all and the n8n editor shows an empty canvas instead of an error.

  Source: https://github.com/czlonkowski/n8n-mcp/issues/90#issuecomment-3128136037 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @naXa777 tried on GitHub (Outcome unclear)

  A maintainer suggested opening the workflow in the n8n editor, inspecting the browser DevTools Network tab, and extracting the workflow JSON from a request response to use as a debug artifact.

  Source: https://github.com/czlonkowski/n8n-mcp/issues/90#issuecomment-3128159915 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport