Why Am I Receiving a 404 Error When Connecting to Bubble's Data API via n8n?

Below are a few additional steps you can take to troubleshoot and resolve the 404 error when connecting to Bubble using n8n:

Verify Your App Name and URL Format

• Extracting the App Name:
  When you view the Data API root URL on Bubble (for example,
  https://n8n-integration.bubbleapps.io/version-test/api/1.1/obj),
  you only need the part between “https://” and “.bubbleapps.io”. In this example, the Dashboard configuration in n8n should use “n8n-integration” as the App Name.

• Using the Correct Endpoint:
  Make sure that the URL in n8n isn’t the main page URL for your Bubble app. The credentials must be configured to point to the Data API endpoint rather than your app’s landing page. Double-check there are no extra characters or slashes in your URL settings.

Confirm Environment & Hosting Settings

• Environment Setting:
  If your Bubble app isn’t yet deployed, make sure you select Development. For a deployed app, choose Live in n8n’s credentials.

• Hosting Setting:
  If you’re using a custom domain for your Bubble app, use the Self Hosted option and ensure you enter the correct custom Domain. Otherwise, if you’re on Bubble’s hosting then select Bubble Hosting.

Revisit the API Token & Data API Settings

• API Token:
  Generate a new API token from the Bubble app’s API tab (if not done already) and copy the resulting Private key into n8n as the API token.

• Data API Enabled:
  Although you mentioned the Data API is enabled, it’s worth double-checking that in your Bubble app’s settings under the API tab the “Enable Data API” checkbox is indeed selected.

Test and Confirm

• Test in Isolation:
  Try using a tool like Postman or CURL with the exact same Data API URL and headers (using your API token) to ascertain that you can retrieve the object data. If the API consistently returns the full app page data, then the issue might be on the Bubble side.

• Double-check Credentials:
  Ensure that the credentials you’re using for the various environments (live, dev, self hosted, bubble) exactly match the expected formats, especially when changing from a Bubble apps URL to a custom domain.

Taking these steps should help narrow down whether the issue is due to a misconfiguration of the Bubble credentials in n8n or a misinterpretation of the endpoint being called. If you re-check your App Name extraction, API token, environment, and hosting settings and still encounter the issue, it may be helpful to test connectivity externally to confirm that the Data API endpoint functions as expected.