Make.com can connect to my self-hosted NocoDB instance, but it cannot load any data anymore

Questions
,
1

:bullseye: What is your goal?

I want Make.com to work properly with my self-hosted open-source NocoDB instance like before, including loading tables and data normally.

:thinking: What is the problem & what have you tried?

Previously, Make.com worked perfectly with my self-hosted NocoDB setup. However, recently it stopped loading data from NocoDB. The connection itself appears successful, but Make.com cannot retrieve or display any tables/data from NocoDB.

What I have tried:

Reconnecting the NocoDB connection in Make.com
Restarting the NocoDB server
Checking API accessibility
Verifying that NocoDB is still running normally
Testing with different modules/scenarios

The issue still persists.

:clipboard: Error messages or input/output bundles

The connection is established successfully, but the data does not load.

:link: Create public scenario page

https://eu1.make.com/221182/scenarios/2318906/edit

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

noco-db-error.png
noco-db-error.png573Ă—662 34 KB

3

Hi @avaboot1,

404 indicates that the module is trying to reach a resource that cannot be found. Have you tried to investigate what Make is actually sending? You can use the Make DevTool for that.

Have you tried the Make DevTool before? It is a Chrome Extension that gives you access to the actual requests and responses that are sent and received by your scenario. Chrome Extension: Make DevTool - Chrome Web Store

Tutorial: Introduction to Make Chrome DevTool (formerly Integromat DevTool)

Cheers,
Henk

4

I also tested with NocoDB Cloud, and the result is exactly the same.

The main issue is that Make cannot load any Workspace or Table data at all. It only shows that the connection is successful, but after that it returns nothing (zero data). This happens with both self-hosted NocoDB and NocoDB Cloud.

Because Make cannot retrieve any data from NocoDB, it is impossible to map incoming or outgoing fields in the scenarios. That is why I do not think using Chrome DevTool is necessary at this stage.

This clearly looks like a system-level issue rather than a user-side configuration problem.

Previously, connecting Make with NocoDB was very easy and worked perfectly without any special troubleshooting.

5

Welcome to the Make community!

This definitely looks like a bug.

Contact Make Support

As this is a community (peer-led) forum, we can only help with using the Make platform as intended (scenario building, troubleshooting scenario/module error messages, etc.). We cannot assist with account, billing, platform availability, technical issues, or bugs with the underlying software.

Make support has access to your specific account details, scenario, execution history, server-side logs, and has internal tools to investigate the issue further. If the issue is with a custom app, Make support will be able to reach out to the external team responsible for maintaining it. Also, you might need to share potentially sensitive information about your account, organisation, scenario, and execution history logs, which is not advisable here on this public forum.

Search for Updates First

Before creating a support ticket, do try to look around if others are facing the same problem, and if there are further steps you can take. Here are some things you can do —

  1. Check the Make Status page to see if it is an ongoing network-wide issue/outage and view any updates (example).

  2. Search this Make forum to see if there are any discussions, updates, and workarounds. Here are some possible search terms you can use:
    tags:error  bug  "not working"

How to Create a Support Ticket

  • If you are unable to log-in, you should use this form to report and resolve your account’s login issue first.

  • When you are logged in to your account, head to the new ticket page to submit a ticket.
    Screenshot of the Contact Support page
    Above: Screenshot of the Contact Support page

After submitting your support ticket, you should receive a confirmation email with the subject “Ticket Created” together with a summary of what you submitted. If you do not receive this automated reply within minutes, try creating a ticket again. Example of email subject: [#1234567] Ticket created | Technical challenge

Priority of Tickets

If you do not receive a response from Make support, simply be patient. Make support receives thousands of tickets, hence tickets have to be prioritised based on the severity of the incidents and organisation’s plan. For more information about the different levels of customer support for each plan, refer to the “Support” section on the Pricing page, or on your organisation’s Subscription page. If you are a free customer, you can create a temporary free Pro account to get quicker support via the ticketing system.

Resolution

When your ticket has an update and/or issue is resolved, we’d love to hear details about it, and how support and you worked to resolve it (including use of any workarounds). By posting your findings and solutions in this thread, we are contributing to this knowledgebase to enable others with similar problems to search for answers.

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!

6

Since auth succeeds but tables don’t enumerate, I’d first compare what the NocoDB API returns directly vs what Make’s connector sees. A quick raw HTTP module test against the same endpoint should tell you whether this is a connector parsing issue or a NocoDB-side/API change.

7

I tested further.

The same NocoDB project/API token works fine in n8n, and direct API calls to the records endpoint also work in Make HTTP:

GET /api/v2/tables/{tableId}/records → 200 OK

However, Make/NocoDB table discovery fails because the meta endpoint returns:

GET /api/v2/meta/bases/{baseId}/tables
→ ERR_FORBIDDEN: API token does not have permission to tableList

So this does not look like a general NocoDB authentication issue. The token works for actual table data and also works in n8n. The problem seems specific to how Make’s native NocoDB connector discovers/enumerates tables, or which NocoDB meta permission/endpoint it requires.

Raw HTTP in Make is a workaround, but the native NocoDB module still cannot load tables.

8

From my testing so far, open-source automation platforms like n8n seem to connect to NocoDB without issues using the older/direct approach.

However, more closed/proprietary platforms such as Make, Zapier, and Latenode are currently unable to properly enumerate/load tables in my tests — both on NocoDB Cloud and self-hosted instances.

I’m not a developer, so I may be missing some technical details, but after reading through the API behavior and testing different platforms carefully, it seems possible that this is related to differences in how newer integrations interact with the NocoDB Meta API / permissions system.

For now, direct HTTP/API calls still work as a workaround, so perhaps we’ll need to wait for clarification or updates from the NocoDB and integration teams.