JSON Payload values in a JSON payload builder step

[PJ 3000]

I have an action that creates a payload using 5 payload builder steps

The last step, number 6 uses the payload generated in step 2 as the value on one of the name pairs.

The output looks fine, until tested, where it shows that the value of that payload contains a slot of escape /" in the payload.  Which is clearly not what i want.

STEP 6 PAYLOAD

STEP 2 PAYLOAD

Is there a way without using JSON Parser as the client doesn't have the integration hub standard license just starter and without scripting the whole REST again.  Is there a way to just format that payload so it doesn't have the slashes in the payload.

[vikasgc1999]

Hi @Richard Hine , @PJ 3000 @adrian08 

How to implement json builder for below example

{

  "name": "John Doe",

  "age": 30,

  "isStudent": false,

  "friends": ["Jane", "Alex", "Michael"],

  "address": {

    "city": "New York",

    "country": "USA"

  },

  "isMarried": null

}

[adrian08]

There's one more weird thing that Payload builder does. It keeps adding quotes. Says the output is not a string, but a True/False, if you pass that to the payload builder step, it does this:
{
"enable_item": "true"
}

My expectation is

{
"enable_item": true
}

[andresrivero]

Which is odd because the standard is to NOT quote boolean values