Ian P.

I have tried setting the JWT Token Endpoint to webhook.site to see the exact request coming from Clay and issuing an identical request to my API works fine. I have tried a different domain for the API (similarly works fine in curl) to see if the domain was blocked, simpler passwords, but just keep getting this error. I can use the normal HTTP API module in Clay to POST to this JWT endpoint and I get the expected response without error.

So far it seems like the easiest way to approach this is with a custom header that includes all of the fields we want to monitor in any order. I originally tried the same concept with the JSON request body (wrapping all fields in one set of quotes) but it looks like there may be a bug rendering adjacent interpolated values inside a JSON string (second screenshot) and this also seems more error-prone than a header that can safely be ignored. First attempt was a run condition like true || /Issued || /Website || /Tradename but that didn't trigger the request to re-run on changes to those fields (understandably). I like it, this is easy enough for me to document and makes it crystal clear that triggering the HTTP call on updates is not done by "magic."

Thank you! That makes a lot of sense. This is an oddball case since we're trying to avoid sending the full data and introducing a maintenance headache in the API call config, but I have a few ideas to tets now that could work.

That information confirms the behavior that I was seeing. I would like to submit a feature request for a 205 status response to bypass the 24 hour timeout so that running the entire row will re-run the HTTP API column as well, or a similar setting to allow that behavior to be configured in Clay.