Troubleshooting HTTP API Action and Field Configuration Issues | Clay

Troubleshooting HTTP API Action and Field Configuration Issues

Hey all... I had this HTTP API action working, and then changed it to replace a constant "No" in the "zaypqLead" field with one that points to the "quote_lead" field (which is a text field that says "Yes" or "No". Bo (. from Clay Support "fixed" it in the version on the right, but I don't know what he changed (and I need to get this working in other tables). My theory is that clay thinks this new field is empty when it's not... So, two questions:

1.
can anyone spot what's different?
2.
is there a way to get the "rendered" output that is trying to be parsed?

Their suggestion to use ChatGPT to check JSON errors isn't helpful — it includes the field widgets...

21 comments

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Ryan H.
·
·
https://app.clay.com/workspaces/242259/tables/t_IHzd1TaLMdwI/views/gv_luPPCfFPbjW2
Muhammad S.
·
·
remove quotes around partner portal id and partner company id field on the left and it should be good,
Muhammad S.
·
·
\
Ryan H.
·
·
yeah. working on it. I've done that. I don't understand why that would be better... checking.
Muhammad S.
·
·
because it is expecting an integer(ID) I guess and its getting a string
Ryan H.
·
·
no dice
Ryan H.
·
·
Ryan H.
·
·
is there a way to see what they're attempting to parse?
Ryan H.
·
·
One difference I see is that the "clay fix" includes an empty space between the "quote_lead" and the closing quote...
Ryan H.
·
·
sigh... removed that and the clay fix still works. 🤷 🤬
Ryan H.
·
·
again... need to understand WHY theirs works...
Muhammad S.
·
·
copy that whole input body that works <> create a text column <> paste it there Then copy that does not work paste it in a nnew text column Then you can visualize the data
Muhammad S.
·
·
to see why something does not work
Ryan H.
·
·
copying and pasting between the clay fix into a new HTTP API column works.... I really wish I could understand what the difference is (maybe a new column is the fix)... but at least I'm unblocked
Ryan H.
·
·
You can't — the widgets mess it up
Muhammad S.
·
·
you can for sure save it and then visualize the column

Ryan H.

{
  "eventType": "enrichmentComplete",
  "partnerPortalId": 



Partner Portal Id



,
  "partnerCompanyId": 



Partner Company Id



,
  "zaybraLead": "No",
  "orcaLead": "



orca_lead



",
  "zaypqLead": "



quote_lead



",
  "otherLead": "No",
  "usesHubspot": "



usesHubspot



",
  "eventsContext": "



Events Context



"
}

Muhammad S.
·
·
create a text column <> click on edit column and paste the body there
Bruno R.
·
·
Hi Ryan, thanks for reaching out. Saw that you were able to set this up in the meantime, sorry about the delay and thank you Muhammad for weighing in on this. To clarify our updates on the HTTP API enrichment columns: In JSON, numbers are unquoted to enable arithmetic operations, while strings are quoted to preserve their exact format, including special characters or leading zeros. Quotation marks distinguish text data from numeric values for parsing and accurate data interpretation. In our recent update to the HTTP API enrichment column, we aligned it with standard JSON structuring practices. I hope this was helpful. If there's anything else I can assist you with, please let me know!
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.