Trouble Connecting NocoDB with n8n – Unauthorized / API Not Found

[FrolsonDev]

Hello,

I’m currently trying to connect NocoDB and n8n, but I’m encountering issues and haven’t found a solution in the documentation or forums.

Here’s my docker-compose setup for NocoDB:

yaml

CopierModifier

nocodb:
  image: nocodb/nocodb:latest
  container_name: nocodb-postgres
  ports:
    - "8080:8080"
  volumes:
    - nocodb-data:/usr/app/data
  environment:
    NC_DB: pg://db:${POSTGRES_PORT:-5432}?u=${POSTGRES_USER:-postgres}&p=${POSTGRES_PASSWORD}&d=${POSTGRES_DB:-postgres}&s=public
    NC_AUTH_JWT_SECRET: "569a1821-0a93-45e8-87ab-eb857f20a010"
  networks:
    - supabase-network
  depends_on:
    db:
      condition: service_healthy
  restart: unless-stopped

The NocoDB dashboard is working properly, and the connection to Postgres seems fine.

I created an API token via the NocoDB dashboard and used it in n8n’s credentials with the host set to:
http://nocodb-postgres:8080

However, the connection fails, and the following logs appear:

swift

[Nest] 8 - 05/05/2025, 7:22:44 AM DEBUG [GlobalExceptionFilter] Cannot GET /api/v1/workspaces/
[Nest] 8 - 05/05/2025, 7:22:44 AM DEBUG [GlobalExceptionFilter] NotFoundException: Cannot GET /api/v1/workspaces/
…
UnauthorizedException: Unauthorized
…
response: { message: ‘Unauthorized’, statusCode: 401 },
status: 401,

It seems that either:

* The endpoint `/api/v1/workspaces/` is incorrect, or
* Authentication with the token is failing (401 Unauthorized)

I’d appreciate any guidance on how to correctly configure the NocoDB connection in n8n, or how to properly authenticate with the API.

Thanks in advance!

[mertmit]

Hi @FrolsonDev
First error Cannot GET /api/v1/workspaces/ is not blocker in OSS there is only one workspace so you can proceed ‘No Workspace’ option.

It seems the issue is your API Token, make sure you are using a valid API Token
You can follow our docs on how to get one.

Also make sure you are selecting API Token on n8n side, User Token is there for backward compatability and no more recommended to use.

Here is a fresh installation using docker for both