URGENT - HTTP PARSER BUG:
HTTP payload isn't getting parsed properly. Existing column: [HTTP] Ping Serper works just fine. But when duplicating it with the EXACT SAME settings, something must happen in the background by Clay manipulating the body, since now we get an 400 error for the duplicated column [HTTP] Ping Serper (2).
I changed the payload for [HTTP] Ping Serper and now it doesn't work anymore. Something must happen on Clay's site that the "q" parameter isn't being sent to the endpoint correctly.
Hey David! Yup, sorry about that issue. I'm currently checking this out with the team since there were updates on how this HTTP module handles requests now with new columns. Here's the video for context but checking how we can format this request so it works for you. https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440?sid=6a65eb66-dc3f-465f-a441-99aee9bb1c56
Not currently, at least not the batch request you're sending in the body. Individual requests should work. Of course, I'm checking with them right now and will let you know how it can be handled soon.
okay, if you can, please keep me updated on this Arturo
It's funny, because all of our old HTTP columns still work, just the new ones do not handle the payload correctly. Maybe that helps you guys to investigate this
Feel free to send it to us yes, I'll send this to the engineer as well :)
Yup, that's correct, David. Old columns weren't affected by the changes. Their looking into implementing a more permanent fix soon, but for now they resolved the issue from the new column by removing any JSON.stringify or Clay.formatForJSON protocols, just inserting the token itself works. Appreciate the feedback and for flagging this one!
Thanks Arturo, that worked perfectly for now!