HTTP trigger - Pipedream fails to parse JSON as object

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Aleem Mawani : did something change with the webhook trigger? Seems that the event body isn’t parsed as json anymore (even if there is a content-type: application/json header). Just getting back a big single string and can’t refer to any of the embeded json fields.

2

Dylan Sather (Pipedream) : I just tested an HTTP POST request with JSON and it parsed OK for me. Can you copy the string you’re seeing in the UI and validate that it’s JSON using https://jsonlint.com/ ? Or run JSON.parse on the body in a Node.js code step?

You’ll see a string as the body in cases where we tried to parse the data as JSON, but failed to because the JSON was malformed in some way.

If you’re still seeing issues and it parses correctly as JSON, could you send me an example payload that shows up as a string, and I can take a look?

3

Aleem Mawani : sorry this is my fault, the JSON was malformed

4

Dylan Sather (Pipedream) : No worries, thanks for the follow up