Hey, The issues with custom fields and GoHighlevel is still happening. Has this been resolved or it’s just me? Thanks
I"m having the same error as of today so my guess is this is still pending resolution.
1 Like
Looks like this is a dead end which wont be fixed and we may have to live with a workaround 
I’ll see if I can create up a small workflow for the workaround over the weekend and share it here - still going to be a fair bit on manual work each time though I feel
It will be fixed but the priority sadly keeps slipping, I know where the change needs to be made the only bit I am not sure about is the API is now under “locations” so we need to work out what a “location” actually is to see how it relates to a contact and how that relates to a custom field.
If anyone wants to give it a go I will happily review it, the line of code that need changing is here: n8n/packages/nodes-base/nodes/HighLevel/v2/description/ContactDescription.ts at master · n8n-io/n8n · GitHub
A location is a sub-account. Each sub-account is a business “location”. They did change the endpoints a little while back when they moved to moved to v2 and redacted v1.
All custom fields, values, tags etc that are in each sub-account are now under locations/{locationId}/ and the locationID is returned in contact GET response
Not sure what the upstream url is but I am assuming the line will need to read as below 
url: '/locations/{locationId}/customFields',
Contact GET Response
Custom Fields
1 Like
How can we test the above to see if it works?
Should I just edit the line and create a PR?
This seems to be lingering on with what seems could be an easy fix with some url edits
Hey @gleeballs
This should be fixed this week, there is a PR in that I need to review and merge.
2 Likes
This is great news. Will await the update.
Great news, Jhon. Thanks a lot for help us that!
Checking back in. Any updates?
No I didn’t get a chance to review it, sorry. Will do it this weekend.
Hey @Jon any new on this?
It’s been 6 months now and I get that it might not be top top priority but there have been other bugs get reported and squashed very quickly and this always seems to get dropped or missed.
How are we sure the updates actually work as they “should”. Could we get a “alpha/beta” v3 node to test before its generally released perhaps?
Have the private integrations been implemented or will it still require the troublesome OAuth security?
Lots of questions…
@jan @Jon @bartv sorry to tag everyone but just wondering if there was any update to this and the HighLevel node in general.
There are bugs going on 6 months, there are api & auth updates and it seems everything is falling on deaf ears.
Is anything happening with this?
I am happy to help test out an alpha/beta release etc if needed. Is any more information required from HL to help complete etc?
Hey @gleeballs
No update yet, once again other bugs with a higher priority that impact more popular nodes had to be fixed first.
This will be resolved but it likely won’t be until January now, there is still a PR I want to review that may fix this as well but if you wanted to put in a PR to fix this we can review that as well, our code is available so if you believe you are able to fix this we would happily accept the PR.
This isn’t hasn’t “fallen on deaf ears” as you have suggested we just need to prioritise what is fixed based on node popularity, users with the issue and if there is a workaround available.
In this case an http request node can be used as a workaround so the priority is not as urgent as some of the other fixes we have done.