Clay's JSON Formatting Function Issue with Empty Values

David · 2025-05-07 14:08:19.643144+00

How come Clay's JSON formatting function not handling empty value properly anymore? Table: Integration: `[PushTo] -> 3b. Export Preparation`

Clay's JSON Formatting Function Issue with Empty Values | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
The issue might be related to the "Remove null & undefined values" option in your HTTP API integration. This feature is designed to remove empty values from your JSON request to prevent potential errors. For the "[PushTo] -> 3b. Export Preparation" integration, check if this toggle is enabled or disabled based on your needs: 1. Go to your integration settings 2. Look for the "Remove null & undefined values" option 3. Toggle it on if you want to remove empty values 4. Toggle it off if you need to preserve empty values in your JSON Could you share your specific JSON so I can help troubleshoot further?
Sources: HTTP API with JWT Authentication with Clay HTTP API with JWT authentication | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
David
·
·
Doesn't solve the issue. Not sure what is patched by the team to the body formatting of HTTP requests, but it changes every month and starts to add unnecessary workload on our team, as we always have to debug it.
Daniela D.
·
·
Hey David! Apologies for the delay. The team was at a company offsite. I noticed you ran this successfully in a duplicate column by sending the entire JSON string. To handle empty values in HTTP API, you need to toggle the "Remove empty fields" option on. I noticed this wasn't enabled for the first column. This should help to prevent sending blank values to the API or errors caused by missing information. Let me know if that helps.
(29 kB)
David
·
·
It was on first. Didn’t work either. Then I turned it off to see if it would change anything .
Daniela D.
·
·
Hey David! Thanks for the reply. We'll look into this and get back with an update. Apologies for the inconvenience🙏🏾.
Daniela D.
·
·
Hey David! Thanks for your patience. I made a quick recording showing how we resolved this: https://www.loom.com/share/2b5ba5f1bc1e4beca0ce9a918c12d803 Additional guide on JSON input in the body section: https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440 Let me know if you still run into any issues.

Channeled
APP
·
·
The issue might be related to the "Remove null & undefined values" option in your HTTP API integration. This feature is designed to remove empty values from your JSON request to prevent potential errors. For the "[PushTo] -> 3b. Export Preparation" integration, check if this toggle is enabled or disabled based on your needs: 1. Go to your integration settings 2. Look for the "Remove null & undefined values" option 3. Toggle it on if you want to remove empty values 4. Toggle it off if you need to preserve empty values in your JSON Could you share your specific JSON so I can help troubleshoot further?
Sources: HTTP API with JWT Authentication with Clay HTTP API with JWT authentication | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
David
·
·
Doesn't solve the issue. Not sure what is patched by the team to the body formatting of HTTP requests, but it changes every month and starts to add unnecessary workload on our team, as we always have to debug it.
Daniela D.
·
·
Hey David! Apologies for the delay. The team was at a company offsite. I noticed you ran this successfully in a duplicate column by sending the entire JSON string. To handle empty values in HTTP API, you need to toggle the "Remove empty fields" option on. I noticed this wasn't enabled for the first column. This should help to prevent sending blank values to the API or errors caused by missing information. Let me know if that helps.
(29 kB)
David
·
·
It was on first. Didn’t work either. Then I turned it off to see if it would change anything .
Daniela D.
·
·
Hey David! Thanks for the reply. We'll look into this and get back with an update. Apologies for the inconvenience🙏🏾.
Daniela D.
·
·
Hey David! Thanks for your patience. I made a quick recording showing how we resolved this: https://www.loom.com/share/2b5ba5f1bc1e4beca0ce9a918c12d803 Additional guide on JSON input in the body section: https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440 Let me know if you still run into any issues.