Help Needed: Unexpected Custom Values Update in GHL API Integration

[Svantomation]

Your Task History ID

IjU3NjUwNTZjMDYzNTA0MzU1MjZlNTUzMTUxMzU1MTYzNTQzNzBmMzEi_pc

Hello guys,

Hello,

I'm encountering an issue while sending API requests to update custom values in GoHighLevel (GHL). Here's the problem:

• The API request is supposed to update specific custom values based on my workflow.
• However, custom values that are not part of my workflow are also being affected.

I suspect this might be due to some sort of caching issue, but I’m not entirely sure.

Could anyone guide me on the following?

1. Clearing Cache: Is there a way to clear any cache in GHL or Pabbly that might be causing this?
2. Identifying Automation Issues: How can I track down which automation or process is unexpectedly sending data to the API? Especially when there’s no visible module or setup in my workflow for those values.

Any help or troubleshooting tips would be greatly appreciated!

Thanks in advance!

 

[Preeti Paryani]

Hello @Svantomation

Upon reviewing your workflow, we noticed that you are using the GoHighLevel v1 API. For GoHighLevel, we have an application named LeadConnector V2, which uses the latest API version.

We recommend creating your workflow to use LeadConnector V2 (as shown in the screenshot) and testing it. Please let us know if this resolves the issue.