HELP: API Response Capture Returns "0" Despite Successful Call
I'm building a product recommendation system using Make.com webhooks to send data to Voiceflow's API block, tested across two separate projects (WooCommerce and Google Sheets integrations). The entire data flow works perfectly - Make.com receives the request, processes and aggregates the data, and the Webhook Response module clearly shows the complete product list in its bundle. Voiceflow's API block confirms success with a 200 status code. Yet the captured response variable in Voiceflow contains "0" instead of the actual data.
This is physically impossible if the system worked correctly. The webhook response bundle in Make.com contains a full formatted list of products with names, prices, descriptions, and links. This exact data should appear in Voiceflow's response variable, but instead it's just "0". It's as if during the transfer between Make.com's response and Voiceflow's capture mechanism, the entire response body gets transformed or lost, despite the API call succeeding.
The logic is undeniable: if the webhook receives the request AND returns valid data (visible in Make.com's logs) AND the API call succeeds (200 status in Voiceflow), then the captured variable MUST contain that data. There's no configuration between these points that could cause this. The same exact issue happens in both my WooCommerce project and my Google Sheets project, proving this might be a systematic problem with Voiceflow's response parser, at least this is what makes the most sense.
This completely breaks any external data integration. I've spent weeks on this with no solution because there's nothing to fix on my end - the bug is in Voiceflow's response capture mechanism. Is this a known parsing issue? Why does valid, successfully returned data become "0"?
This is physically impossible if the system worked correctly. The webhook response bundle in Make.com contains a full formatted list of products with names, prices, descriptions, and links. This exact data should appear in Voiceflow's response variable, but instead it's just "0". It's as if during the transfer between Make.com's response and Voiceflow's capture mechanism, the entire response body gets transformed or lost, despite the API call succeeding.
The logic is undeniable: if the webhook receives the request AND returns valid data (visible in Make.com's logs) AND the API call succeeds (200 status in Voiceflow), then the captured variable MUST contain that data. There's no configuration between these points that could cause this. The same exact issue happens in both my WooCommerce project and my Google Sheets project, proving this might be a systematic problem with Voiceflow's response parser, at least this is what makes the most sense.
This completely breaks any external data integration. I've spent weeks on this with no solution because there's nothing to fix on my end - the bug is in Voiceflow's response capture mechanism. Is this a known parsing issue? Why does valid, successfully returned data become "0"?
