Skip to content
Troubleshooting Cus...
 
Notifications
Clear all

Troubleshooting Custom Field Updates in HighLevel via HTTP Request PUT

20 Posts
8 Users
0 Reactions
8 Views
Carlos_Guimaraes
(@carlos_guimaraes)
Posts: 5
Active Member
 

Any updates on this matter?

 
Posted : 11/08/2024 1:00 am
CHAD_GRAY
(@chad_gray)
Posts: 1
New Member
 

Is this still not functioning correctly?

Could you please provide the rewritten markdown content? It should be in markdown format.

 
Posted : 12/08/2024 7:50 am
Jon
 Jon
(@jon)
Posts: 96
Trusted Member
 

This is next in my queue to address.

 
Posted : 12/08/2024 10:52 am
gleeballs
(@gleeballs)
Posts: 9
Active Member
 

It would be beneficial if the node could be updated concurrently to support Private Integrations.

Essentially, reverting to the previous method of using an API key instead of OAuth, which might be simpler as OAuth sometimes presented challenges.

Private Integrations offer greater power by utilizing the v2 API and are more adaptable than the OAuth approach. They are considerably easier to implement and manage within sub-accounts.

 
Posted : 19/08/2024 5:05 am
gleeballs
(@gleeballs)
Posts: 9
Active Member
 

Just checking for any recent developments on this.

Specifically, are custom fields being fixed, or are private integrations being introduced?

Alternatively, could the v1 node be reinstated, as it was functional?

 
Posted : 18/09/2024 6:45 pm
Page 2 / 2
Share: