n8n NocoDB Node Not Retrieving Project and Table Names in Cloud Version

Based on the NocoDB credentials documentation, the connection test only verifies that the API key and host (in your case, https://app.nocodb.com) are working and that basic connectivity is established. It does not guarantee that all endpoints (such as those for listing projects or table names) will return data.

A few points to consider:

1. API Endpoints vs. Credential Test:
   The connection test confirms that your API token is valid and that n8n can reach the NocoDB Cloud instance. However, the node’s value loading (listing projects/tables) relies on specific endpoints that may behave differently on the cloud version.

2. Cloud Instance Limitations:
   While the NocoDB documentation for credentials is written with both self‑hosted and cloud versions in mind, the cloud version (app.nocodb.com) might not expose the same endpoints for listing projects or tables as a self‑hosted instance. This can result in the node not retrieving the required names even though the connection test passes.

3. Permissions and API Scope:
   Double‑check that your API token (generated from the account settings in NocoDB) has sufficient permissions to list or view the projects and tables. Sometimes, even though the token is valid, its access scope might be limited.

4. Workarounds:
   • If the cloud instance doesn’t support listing these values automatically, you may need to manually enter the project or table names in your workflow configuration.
   • Alternatively, consider contacting NocoDB support or checking their documentation/forum to see if there’s an update or known limitation regarding this behavior on the cloud service.

To summarize, the issue you’re experiencing is most likely due to limitations or differences in the API endpoints available on the NocoDB cloud version rather than an n8n issue. You might need to work around this by manually setting the values or confirming with NocoDB if the cloud-hosted API supports auto‑discovery of projects and tables.

Below is a quick checklist to help you troubleshoot:

1. Verify Community Node Availability

Even though the credential test passes, if you’re using a community (custom) node for NocoDB you must ensure its packages are loaded on startup. In Docker this means:

• Persisting your n8n directory, including the “nodes” folder, so that the community node files aren’t lost between container updates
• Alternatively, set the environment variable N8N_REINSTALL_MISSING_PACKAGES=true to reinstall missing packages automatically (note this may slow your startup)

2. Check Permissions on the Cloud API

Although you can test the API key successfully with the host https://app.nocodb.com, certain endpoints (like those returning project or table names) might need extra permissions. Verify that your API key is authorized to list projects and tables in NocoDB Cloud.

3. Confirm Endpoint Behavior

Since you’re on the cloud version, it’s useful to double-check whether the endpoints used by the node to fetch projects/tables are supported or if they differ from a self-hosted instance. Compare with any available NocoDB Cloud API documentation or reach out to their support if necessary.

4. Enable Debug Logs

Launching n8n with debug logs enabled (for example, by setting LOG_LEVEL=debug) can reveal if there’s an error when querying projects or tables. This extra detail may point to a misconfiguration or to differences in the API.

If after these steps you continue to have trouble, consider posting details (including your Docker setup and any debug logs that might indicate errors) on the n8n community forum. This can help isolate whether the issue is with how the community node is packaged or if it’s an incompatibility with NocoDB Cloud’s API.