Custom Fields Update in HighLevel Using HighLevel Node or HTTP Request PUT Not Working

This should have been resolved in 1.74.0 which also added the option to use calendar items if that isn’t the case let me know and I will put this to the top of my list for next weeks release.

This is still not working, and I’m on version 1.75.2. I’m having the same issues as the other users.

It’s working for me now however, i needed to update the scopes to include location.readonly, write etc… if you’ve done this already and still having trouble then the team will need to have a look. Hopefully it’s something simple.

What version are you on @A_Bradley ?

I recently updated to 1.76.1

Yes I have those scopes and I am still getting an error on the latest version.

Hello,

The lists appears if you have the scopes: locations/customFields.write and locations/customFields.readonly

However updating a lead doesn’t work when using the highlevel node but it works using an HTTP request with custom fields into the body:

{
“customFields”: [
{
“id”: “osq810kAboealDcCedOO”,
“key”: “call_id”,
“field_value”: “{{ $(‘Webhook’).item.json.body.call_id }}”
},
{
“id”: “EcAkqkIvyy4hKTF2WubK”,
“key”: “call_transcript”,
“field_value”: {{ JSON.stringify($(‘Webhook’).item.json.body.concatenated_transcript) }}
},
{
“id”: “Ut8zjS0JRw8ak5x247aE”,
“key”: “call_lenght”,
“field_value”: “{{ $(‘Webhook’).item.json.body.call_length }}”
}
],
“tags”: [
{{ $(‘HighLevel3’).item.json.tags.map(tag => JSON.stringify(tag)).join(", ") }},
“interest_yes”
]
}

I think the highlevel node is still buggy.

Yes the node is still buggy, this may have been put on the back burner, which is a bummer. @Jon