kyle
Member
- Consent to Access & Modify
- I don't authorize Pabbly Support to log in to my account.
This has been an issue since July 2025, why is this not fixed yet? https://forum.pabbly.com/threads/trigger-response-data.31253/
I’m running into an issue when using Pabbly Webhooks (and other triggers like WhatConverts) where selecting “Raw” as the response format does not return the actual raw JSON.
Instead of giving me the raw JSON as a single block or string, it parses the payload and breaks it into individual fields. This defeats the purpose of choosing “Raw”—I can’t access the full unparsed JSON to pass it into AI models or other tools that expect a true raw string.
Here’s what I’ve tested:
When I choose “Raw JSON Response,” I expect to get the entire JSON payload as a raw text block (as a string, not parsed) so I can forward it or process it myself.
Actual Behavior:
Pabbly still parses the JSON into fields, and I’m unable to access or extract the actual raw string version of the payload.
Please advise if there’s a workaround or if this is a bug. I really need the raw JSON preserved for AI integration purposes.
I’m running into an issue when using Pabbly Webhooks (and other triggers like WhatConverts) where selecting “Raw” as the response format does not return the actual raw JSON.
Instead of giving me the raw JSON as a single block or string, it parses the payload and breaks it into individual fields. This defeats the purpose of choosing “Raw”—I can’t access the full unparsed JSON to pass it into AI models or other tools that expect a true raw string.
Here’s what I’ve tested:
- Webhook trigger with “Raw” response format selected.
- Also tested with WhatConverts as a trigger.
- In both cases, Pabbly still parses the JSON and exposes fields instead of giving the raw payload.
When I choose “Raw JSON Response,” I expect to get the entire JSON payload as a raw text block (as a string, not parsed) so I can forward it or process it myself.
Actual Behavior:
Pabbly still parses the JSON into fields, and I’m unable to access or extract the actual raw string version of the payload.
Please advise if there’s a workaround or if this is a bug. I really need the raw JSON preserved for AI integration purposes.
Last edited:
