any way to debug this?

👋 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!

https://app.clay.com/workspaces/147954/tables/t_nbGMaaP976AQ/views/gv_7SeBHRb9Puar

saw Ryan's post - I created a new column and pasted over the values, but still no dice. all my variables are either text or "links" (which I imagine both are treated as string)

could you share a screenshot of your input body?

changed one of those variables that were wrong lol (title instead of email)

try adding double quotes around the dynamic columns

kk

if that still does not work try adding double quotes around dynamic columns except the salesforce user id

didnt work - also sf ID is still a string

can you try removing quotes around salesforce ID?

i di d

can you create a text column, click on edit column and copy paste this body in there and then pass that text column directly into HTTP body?

also, does all the cells that are dynamic has values in it or not?

all of them have values yes - are you asking to replace dynamic values with string values directly?

no, create a new text column click on edit column then copy paste this whole body in there.

got it

error, but now i see things are double double quoted

yes, you gotta fix them then

okay so back to square one basically but offloading the tokens in http api as text

oh I see a possible issue

the variable 'sample_text' includes double quotes as part of the string

okay that wasnt it

huddle?

thanks - appreciate it

If you want to deal with values that are empty https://clayrunhq.slack.com/archives/C025KSBLPGX/p1721488408696389?thread_ts=1721029251.700579&cid=C025KSBLPGX

looks like even though certain fields are considered "text", Clay does not automatically put double quotes around them (for example, phone numbers). This was also the case for the email type. Thanks for fixing this muhammed!

Hey, thanks for reaching out Vlad - If it's numbers, then yes no quotation mark. This is common for all HTTP API body :) Great job Muhammad ! :)

That's the problem, the field type is text so it should all be considered a string

and it's inconsistent how clay is treating text fields - unless im missing something obvious

similar to the email field type - that should be considered a string and automatically contain the double quotes like other strings

the highlighted fields are ones I had to include double quotes, but you can see that the field types are text. the other text field types I did not need to do this

Hey Vlad 👋, It looks like you may have copied this body from an older version of our HTTP API. In the body, when clicking on the gear icon and selecting Formula, you’ll notice it’s still using the outdated JSON.stringify. However, we should be using` Clay.formatForJSON` instead. I’ve already made the change in a new column, and everything is working as expected now 🎉. The only issue left is with the mobile phone number formatting, but you can easily resolve that by using the Normalize Phone Number formatter. Here’s the link with more details on how to implement it: 👉 Normalize Phone Number with Clay Let me know if you have any other questions or need further assistance! 😊

Bo! Thanks for sharing that, I understand now why I was having the intermittent issues. Can I DM you a question unrelated to this? Feel free to close this 'case' 😄