Unable to Connect Baserow Credentials with N8n

Questions
1

Hey there, I’m new to n8n. I’ve imported someone else’s workflow, but I’m unable to set the Baserow credentials. n8n is currently hosted through Node (or npx) and Baserow is running in a container at the URL: http://localhost:85/

After setting everything up in the credentials, the Baserow node is unable to accept the request, which may be due to an authentication failure as shown in the logs.

2025-04-08 06:42:08  [BACKEND][2025-04-08 01:42:08] 127.0.0.1:54814 - "GET /api/_health/ HTTP/1.1" 200  
2025-04-08 06:42:08  [BACKEND][2025-04-08 01:42:08] WARNING 2025-04-08 01:42:08,961 django.request.log_response:241- Not Found: //api/user/token-auth/   
2025-04-08 06:42:08  [BACKEND][2025-04-08 01:42:08] 172.17.0.1:0 - "POST //api/user/token-auth/ HTTP/1.1" 404  
2025-04-08 06:42:08  [BACKEND][2025-04-08 01:42:08] WARNING 2025-04-08 01:42:08,987 django.request.log_response:241- Not Found: //api/user/token-auth/   
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] 172.17.0.1:0 - "POST //api/user/token-auth/ HTTP/1.1" 404  
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] WARNING 2025-04-08 01:42:09,021 django.request.log_response:241- Not Found: //api/user/token-auth/   
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] 172.17.0.1:0 - "POST //api/user/token-auth/ HTTP/1.1" 404  
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] WARNING 2025-04-08 01:42:09,069 django.request.log_response:241- Not Found: //api/user/token-auth/   
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] 172.17.0.1:0 - "POST //api/user/token-auth/ HTTP/1.1" 404  
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] WARNING 2025-04-08 01:42:09,111 django.request.log_response:241- Not Found: //api/user/token-auth/   
2025-04-08 06:42:09  [BACKEND][2025-04-08 01:42:09] 172.17.0.1:0 - "POST //api/user/token-auth/ HTTP/1.1" 404

forums
forums1176×770 24.5 KB

2

The log messages say Not Found: //api/user... which seems to lead with too many / characters, so, it may get things working to remove the trailing / from the baserow “base” URL, but I’m not sure that will be the whole problem.

The way baserow is coded, this is a little tricky. I got it working a few months back and posted the details here

One part I wasn’t entirely clear about when I made that post is that (I think) it depends, in part, on the hostname being the same inside docker as it is outside docker, so localhost is problematic. If you set the service name within docker to something like mybaserow and put that same hostname in your hosts file outside of docker, mapped to 127.0.0.1, then I think you might be able to get both the baserow web UI and the n8n-docker-container->to->baserow-docker-container api calls working.

3

Thanks for the help! I’m not sure how, but the same credentials started working after I retried about 10 minutes later.

4

Hi @Muhammad_Hilal, how were you able to solve this?

I currently get the invalid credentials error even after inputting the right credentials