GHL OAuth 2.0 400 Error

How To
, ,
1

So I’m literally just trying to connect go high levels lead connect to my account I’ve added all the Scopes that I can see in the URL and the connection but when I click on a sub-account I can’t connect. But if I use the “HTTP OAuth 2” Module I can make a connection load the app with no issue from the marketplace. Any insights on my keep getting this code when I try to use the go high level module. These are scopes that I added
campaigns.readonly
companies.readonly
contacts.readonly
contacts.write
locations.readonly
locations%2FcustomFields.readonly
locations%2FcustomValues.readonly
locations%2Ftags.readonly
opportunities.readonly
opportunities.write
users.readonly
users.write

update: While I was doing this I just let the scenario run a little bit and I noticed this error within the module Failed to verify connection ‘LHM My Highlevel Location OAuth 2.0 connection’. Status Code Error: 422

  • Failed to verify connection ‘LHM My Highlevel Location OAuth 2.0 connection’. Status Code Error: 422

Screenshot 2024-03-14 121536
Screenshot 2024-03-14 1215361589×649 118 KB

1 Like
3

did you get this fixed? I’m having the same issue

4

Same issue. I think Make.com app for GHL oauth 2.0 doesnt work properly, I think its an issue with the Make.com app within GHL. It doesn’t have enough permissions

5

I was having the same issue. It looks like Make finally migrated from the integromat domain. Go back to your Marketplace app and add https://www.make.com/oauth/cb/highlevel4 and https://www.make.com/oauth/cb/highlevel3 instead.

Hope that helps!

1 Like
7

Hello Mavenx,

Thanks for the tooltips but if I get is right we need to add in setting under redirect URLs.
However when we try to add it we have an error that is saying :slight_smile:

The redirect uri contains a Highlevel reference => Please remove any Highlevel reference to save …

Capture d’écran 2024-06-24 à 13.37.25
Capture d’écran 2024-06-24 à 13.37.251784×508 41.5 KB

So for me it doesn’t work.
Is it the right place to add it in GoHighLevle settings ?

Thanks

8

Welcome to the Make community!

Ahh, in that case you’ll need to contact Make support to get us a new GHL “Callback URL” that doesn’t use the banned word “highlevel”.

I looked at the documentation at https://www.make.com/en/help/apps/productivity/highlevel-leadconnector, and it sure is asking us to use https://www.integromat.com/oauth/cb/highlevel3, which GHL will block as shown in the error message in your screenshot.

For technical issues or bugs like this, directly contacting support can often lead to a faster resolution.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

Join the Make Fans Discord server to chat with other makers!

1 Like
9

Thanks @samliew => a new ticket is created !

2 Likes
10

I didn’t get feedback from my ticket yet but I manage to make it work in the meantime for me.

How.

  1. Restart from zero about creating an app on GoHighLevel market place.
    => IMPORTANT : about setting of this new app:
  • App Type: Private.
  • Distribution Type: Agency and Sub-account.
  • Listing Type: Standard (Non white-label).
  1. Setup all access as requested (I don’t test with only what I would need, it will be my next try):
  • companies.readonly
  • campaigns.readonly
  • contacts.readonly
  • contacts.write
  • locations.readonly
  • locations/customValues.readonly
  • locations/customFields.readonly
  • locations/tags.readonly
  • opportunities.readonlyopportunities.readonly
  • opportunities.write
  • users.readonly
  • users.write

find it here:
https://www.make.com/en/help/apps/productivity/highlevel-leadconnector?_gl=1*1ps6dvz*_gcl_au*MTI1NTk3MzM2MC4xNzE5MjI2NTYx*_ga*OTY3MTc5MTMuMTcxOTIyNjU1Ng…_ga_MY0CJTCDSFMTcxOTIyNjU1Ni4xLjEuMTcxOTIzMDQ5MS42MC4wLjA.

  1. Insert URL redirection. The link in the doc is not right. For me I had to put :
    https://www.make.com/oauth/cb/highlevel4
    https://www.make.com/oauth/cb/highlevel3

as it’s a Standard (Non white-label) => It’s working !! My app was define before as a Not standard and it didn’t allow high-level in the URL.

After this. It has worked :slight_smile:

Hope it will help others !

3 Likes
11

Hi @Fab, sorry for the late reply on my part!

But you’re exactly right! You have to change the type to Standard to get rid of that error. I was getting the same errors with the URLs. The Make.com article needs to be updated with the new domain name.

I’m just now having some issues with the scopes and errors from the API to perform certain tasks. I granted all access and it was still not allowing me to do some things.

Glad you were able to figure it out in the meantime!

12

so what is the latest URL

13

You’ll have to ask Make support for that.

For technical issues like this, directly contacting support can often lead to a faster resolution.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). Alternatively, you should be able to send an email to helpdesk@make.com and support@make.com and it should create a ticket. After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

Join the Make Fans Discord server to chat with other makers!