ok, HTTP API. Clay can see the results as data for example in a waterfall (yes these work now π), but they are not visible in the return from an HTTP API. https://www.loom.com/share/8c3f0a2a967e474ca80f27c377ccbb34?sid=41560f8c-ca3b-42da-97bc-11bb7b3ed1b3
The issue you're experiencing might be related to how the HTTP API response is being handled or parsed. To troubleshoot this, we need to look at a few things: 1. Check the "Field Paths to Return" setting in your HTTP API configuration. If specified, only the referenced field paths will be returned. 2. Verify if the "Remove null & undefined values" option is toggled on, as this could affect the returned data. 3. Examine the API response structure to ensure the data is where you expect it to be. To help diagnose the problem, could you please copy and paste the JSON response from the HTTP API into the chat? This will allow us to troubleshoot further and identify any potential parsing issues.
Hey Andreas, great to hear from ya! Good call out. This seems to be related to how the preview is attributing row numbers to these values. For example, this second LinkedIn URL is number 2 in this preview, however on the table itself it actually appears on row 37. This is further confirmed by rows 1, and 3-10 resulting in Missing Input. Appreciate you pointing this out though Andreas! Will try and reproduce this on our end so we can get to a resolution. :) Let us know if you have any other questions!
Thank you so much for sharing your feedback βAndreas W.β!