Unable to Update Phone Number Field in GHL Account via API

Zohaib A. · 2025-01-16 19:11:11.212387+00

Hi team -- QQ Why am I unable to update the Phone Number field in my GHL account? For testing, I added another field, LinkedinURL, and I can successfully update it using the HTTP API. However, the Phone Number field doesn’t update when using a variable in the HTTP API column. Interestingly, if I use a hardcoded Phone Number, the field updates correctly.

Unable to Update Phone Number Field in GHL Account via API | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
This issue is likely related to JSON formatting of dynamic variables in the HTTP API. When using dynamic variables (like your Phone Number field), you need to ensure they are properly formatted: 1. For string values (including phone numbers), you must enclose the dynamic column reference in quotation marks 2. The key (field name) must also be in quotation marksFor example, your JSON body should look like: LBKS{ "phone": "/column" }LBKSThis is a recent requirement as of October 2024 - all dynamic string variables must be enclosed in quotation marks when using the HTTP API enrichment column.If you're still experiencing issues, try these troubleshooting steps: ** Check for any extra spaces or hidden characters ** Verify your JSON syntax (commas, colons, brackets) * Try validating your JSON structure using a tool like JSONLint Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark L.
·
·
Hello Zohaib, thanks for sharing this. In the table you mentioned... https://app.clay.com/workspaces/266968/tables/t_rYKvCzfpju9A/views/gv_2KzuwF6haAoN ...I see 200/success results in the HTTP API column. So I wanted to understand better. - Did you figure this out already? - Or is the issue that it appears to be successful in Clay, but no updates are made on the other side, when you happen to use the variable for the field? Recent requests appear to be supplying the expected "+1234567890" values, but let me know if you're still having trouble.
Zohaib A.
·
·
When I try to push the hardcoded value "+1234567890," I'm able to update the Phone field in my GHL. However, when I attempt to push a phone number using a variable, the Phone field in my GHL contacts doesn't get updated.
Daniela D.
·
·
Hey Zohaib! Thanks for reaching out. Happy to help✨. We noticed the phone number field is now in quotes and set to "Clay.formatForJSON". To confirm, did it fail to populate the phone field for all rows with this configuration?
Channeled
APP
·
·
Hi Zohaib A.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Zohaib A.!

Channeled
APP
·
·
This issue is likely related to JSON formatting of dynamic variables in the HTTP API. When using dynamic variables (like your Phone Number field), you need to ensure they are properly formatted: 1. For string values (including phone numbers), you must enclose the dynamic column reference in quotation marks 2. The key (field name) must also be in quotation marksFor example, your JSON body should look like: LBKS{ "phone": "/column" }LBKSThis is a recent requirement as of October 2024 - all dynamic string variables must be enclosed in quotation marks when using the HTTP API enrichment column.If you're still experiencing issues, try these troubleshooting steps: ** Check for any extra spaces or hidden characters ** Verify your JSON syntax (commas, colons, brackets) * Try validating your JSON structure using a tool like JSONLint Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark L.
·
·
Hello Zohaib, thanks for sharing this. In the table you mentioned... https://app.clay.com/workspaces/266968/tables/t_rYKvCzfpju9A/views/gv_2KzuwF6haAoN ...I see 200/success results in the HTTP API column. So I wanted to understand better. - Did you figure this out already? - Or is the issue that it appears to be successful in Clay, but no updates are made on the other side, when you happen to use the variable for the field? Recent requests appear to be supplying the expected "+1234567890" values, but let me know if you're still having trouble.
Zohaib A.
·
·
When I try to push the hardcoded value "+1234567890," I'm able to update the Phone field in my GHL. However, when I attempt to push a phone number using a variable, the Phone field in my GHL contacts doesn't get updated.
Daniela D.
·
·
Hey Zohaib! Thanks for reaching out. Happy to help✨. We noticed the phone number field is now in quotes and set to "Clay.formatForJSON". To confirm, did it fail to populate the phone field for all rows with this configuration?
Channeled
APP
·
·
Hi Zohaib A.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Zohaib A.!