Cannot connect n8n to highlevel V2 api, getting 400 error. help?

[embodysteve]

I am unable to authorize the highlivel v2 node.
I have followed all the instructions in the N8N and Highlevel documentation, (which is really fragmented…) Ive given the correct details for client key and secret key and callback link.

When I go to connect N8N to highlevel, I get to the point where I am choosing the location to connect to, and it gives me a 400 error, and will not continue.

Ive seen several other threads and topics with this issue, but most were fixed by correcting credential details. Ive checked with high level dev, they said my spacing between scope items was off, there was 2 spaces instead of one. so thats fixed now. also someone mentioned having www in the link (on the high level app side) was important. so thats done. really not much else i can find to correct. ive cleared browser cache, tried multiple browsers. no luck. has anyone else overcome this problem, or has another possible thing to check?

according to the instructions ive added all the required scopes.

locations.readonly
contacts.readonly
contacts.write
opportunities.readonly
opportunities.write
users.readonly

Am self hosting n8n, on version 1.72.1
Thanks for any advice.

N8N version: 1.72.1
Error: 400
no workflow yet, just trying to authorize highlevel v2 api
N8N is running self hosted, via coolify (docker i think)
OS: Ubuntu 22.04

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Jon]

Hey @embodysteve

Is there any text with the error as well? The credential should be working if configured correctly.

[Jay_Knaggs]

HI, the fix for this is double-checking and retyping your scopes; I copied and pasted mine in and continued to get this error. I deleted and retyped them to fix the issue. I hope this helps everyone fix this, as I have found plenty of discussions with no fix made available.