HTTP Request - Highlevel API Help

I’m executing a HTTP request to GET contacts based on their ID and i’m getting a response however, I’m not getting any of the empty fields from Highlevel. My workflow is such that i’m wanting to update one of these fields ( hence why it’s currently empty) however, i’m not receiving them in the payload response. How can I do this?

I’ve read the Highlevel API docs and it outlines the payload response fields and I don’t see a setting somewhere that I’ve missed.

Information on your n8n setup

  • **n8n version: 1.58.2
  • **Database (default: SQLite): Self Hosted at railway.app
  • **n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • **Operating system: macOS

hello, can you share your workflow?

Have you tried using the http request node and call the highlevel API directly? Without using the n8n node? Using the predefined credentials? sometimes a node can be buggy or the service changed something in the api which hasn’t been updated to the n8n node.

Yes. The HTTP node after the “If” node is exactly this. I tried the highlevel update/create customer node and it did not pull any custom fields. My challenge here now is that the HTTP request only returs fields that are not empty. I need it to return the full field payload

By default, n8n should also return empty json values. Have you tried using tools like postman? I guess it has to do something more with the API you are trying to call. I also see this just now: Do you have the full access?

Sometimes it is also useful using the playground of the api to get an successful request and then just copy the curl and import it to n8n. Get Contact | Integrations API

Thanks for sharing this. What’s weird is that i’ve created this workflow in other builders such as Pabbly and Make.com, targeting the same HighLevel Accounts, and have never had the API not return all fields. I experience this issue with both the HTTP request as well as the Highlevel nodes. Is this a bug?

Any additional input on this? Is there a plan to update this node?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.