hi everyone, I’m getting an error when using the NocoDB node in n8n and would love some help.
Setup:
n8n version: 2.9.4 (Self Hosted)
NocoDB version: 0.301.3
Both self-hosted via Docker on a VPS
The error:
responseData.list is not iterable (cannot read property undefined)
What I’ve tried:
Base ID and Table ID are correct (verified directly from NocoDB UI)
API Token credentials are working
Workspace set to “No Workspace”
Turning off “Return All” and setting Limit to 50 → node executes successfully but returns no items, even though the table has data
My theory:
NocoDB v0.301.3 seems to use a newer API format that no longer returns { list: [...] }, which is what the n8n NocoDB node expects. This causes the error when “Return All” is on, and returns empty results when it’s off.
Question:
Is there a known fix for this? Should I downgrade NocoDB to an older version (e.g. 0.202.10)? Or is there a workaround?
it’s not your workflow issue but a mismatch between what the n8n NocoDB node expects and what your current NocoDB API is returning. Changing the API version or matching the node to the correct API should make the Get Many Rows node return proper items instead of throwing that error.
you should pick the API version that your node expects, by using an older NocoDB version or setting the NocoDB node’s API version to match the server (e.g., v0.200.0 or the version your instance supports).
Solution: Try selecting an earlier supported API version (v0.200.0 onwards) that matches your NocoDB server’s API output or try downgrading NocoDB to a version that returns the older response format (one that includes list).
Temporary workaround: you can also use an HTTP Request node to call the NocoDB API directly and parse the returned JSON yourself (e.g., using JSON or Code nodes) then map it into standard n8n items.
Hi @dbtaiyta, welcome to the n8n community!
You could try updating n8n to the latest version first, just to make sure you’re not hitting an issue that has already been fixed in the NocoDB node. If the problem still happens after upgrading, a good alternative is to switch to the HTTP Request node and call the NocoDB API directly using your existing NocoDB credentials, then map the returned array into n8n items manually…And if neither of those options helps, you could temporarily pin or downgrade your NocoDB version to one that’s known to work with your current n8n setup.
Yeah your theory is right, NocoDB 0.301.x uses API v3 which returns records instead of list and the n8n node hasn’t been updated for that yet. Easiest fix is downgrading NocoDB to 0.202.x, or you can bypass the node entirely and hit the v3 API with an HTTP Request node and parse the records array yourself.
Your theory is right, NocoDB changed their API response format in the newer versions and the n8n node hasn’t caught up yet. Easiest fix is just use the HTTP Request node to hit the NocoDB API directly instead of fighting with the built-in node, that way you control exactly how the response gets parsed and you’re not dependent on n8n updating their node code.
