Bubble invalid URL

I’ m usiing bubble node to get an object and I got an invalid URL error.

I set up bubble credencial following the guidelines. Bubble credentials | n8n Docs

I’m doing the exact same request with an http request node, using the exact same token and fuctioned perfecty

This is the credential configuration I have in bubble and the bubble node configuration

and this is how I confogured the https node with same credencial as bubble node

Is bubble node malforming the URL?

I’m facing same issue, there is no proper tutorial on how to properly connect n8n with bubble.io

Can you please share the stack trace?

NodeApiError: Invalid URL at ExecuteContext.bubbleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Bubble/GenericFunctions.ts:56:9) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Bubble/Bubble.node.ts:87:21) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1212:9) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1582:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2153:11

Thank you. Tracking internally here: Linear

Tried to open Linear from link you shared but i dont have access to workspace

some how i have now entered till bubble and its giving this error

Authorization failed - please check your credentials
401 - {“error_class”:“Unauthorized”,“args”:{“code”:“17535549008x126948261809650”},“message”:null,“translation”:“Invalid or expired token: https://xxxxxxxxx.com/version-test/api/1.1/obj?Bearer25ef2b66547e4e25869ffc”}
(I changed the link a bit just for security)

While all is correct i have checked same link at other place working fine and getting data but here it shows error

Stack trace

NodeApiError: Authorization failed - please check your credentials at ExecuteContext.bubbleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Bubble/GenericFunctions.ts:56:9) at processTicksAndRejections (node:internal/process/task_queues:105:5) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Bubble/Bubble.node.ts:87:21) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1212:9) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1582:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2153:11

I faced same issue, you can check some blog tutorials at Bubble.io or Isloo Tools

No help yet on this :frowning:

my bubble app also has a custom domain like yours, but this is what works for development side, even though I have a custom domain, with a custom name. the name is the screenshot is when you’re in the bubble editor, you get “id=“ from the browser URL.

although this worked I am still unable to authenticate credentials for the live version, but they do seem to work on development.

I had the same problem, but I found the solution:
You need to add “https://” to your domain, so you get “https://yourdomain.com” and NOT “yourdomain.com”.