JSON Parser Node

Feature Requests
,
1

The idea is:

As we’re dealing with API’s daily, most of them output a JSON string, which needs to be parsed in order to use it in other nodes in the workflow.
I know it might seems like an unnecessary addition [I’ve used the Code node to parse JSON], but it makes the process easier and cleaner! [been using a similar module in make.com]

image
image728×752 18.4 KB

My use case:

Parse JSON strings

I think it would be beneficial to add this because:

It’s convenient and supaa easyy!

Any resources to support this?

–

:fire::fire::fire: Don’t forget to upvote this request. The more votes this Feature Request gets, the higher the priority.

2

hello @brahimh

Actually, Edit FIelds is able to parse or stringify the JSON

2 Likes
3

Just tried it, it didn’t work for this JSON string for example

image
image500×570 18.7 KB

image
image1436×648 40.9 KB

Tried passing the Json directly as {{$json.data}}, and also pasting it there…

Make’s Parse JSON module:

image
image1050×614 54.4 KB

I already got the result I want using Javascript via the code node, But it’d be very helpful to have a node that can handle all JSON Parse Formats…

4

And what is the issue? I do not see any strings in your example.
you have a JSON object on the screenshot. The Edit Fields node also returns the JSON object. If you want it to return a string, then the type should be “String” and not an “Object”

5

I mean, each “variable” should be separate so I could use it in the next nodes, which’s not the case when using the Edit Fields node.

6

No, It should not be separated as you have a nested Array there.

To be able to see the “variable N” as a separate entry, you will need to output it as
{{$json.data[0]}} in JSON Mode (not the Manual Map)

Or you can simply use the Split Node

1 Like