# Payload data into JSON format

**URL:** <https://forums.losant.com/t/payload-data-into-json-format/4680>\
**Category:** Help\
**Tags:** experience\
**Created:** [August 5, 2022, 9:05pm UTC](https://forums.losant.com/t/payload-data-into-json-format/4680 "2022-08-05T21:05:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cesar\_Guedes](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@Cesar\_Guedes](https://forums.losant.com/u/Cesar_Guedes)\
**Post date:** [August 5, 2022, 9:05pm UTC](https://forums.losant.com/t/payload-data-into-json-format/4680/1 "2022-08-05T21:05:25Z")

</div>

Hello!  
Wanting to show some of my data on an Experiences Page, I tried some different workflows and easily managed to do it. However, I don’t think I have successfully shown the data in the adequate JSON format.  
Using the “JSON Encode” Node, the data was stored in a payload (pageData.jsonFormat). In a pretty basic test page, I simply used:  
 ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/0/05c9d6aecd9a374a28f4761efcd7b6bedc9979ed.png)

and the result seems to be correctly formated:  
 ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/1/106ae07551cb1da86fa9ce0aef8f9c53f94b7419.png)

But I can’t use this payload data in my scripts, and even the JSON viewer extension doesn’t really recognize the data.

I’m sorry if that’s too simple of a question, but how do I correctly convert my page data into Javascript?

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [August 5, 2022, 9:17pm UTC](https://forums.losant.com/t/payload-data-into-json-format/4680/2 "2022-08-05T21:17:07Z")

</div>

It looks like your data, while resembling an object, is actually in the form of a string, which would explain why you cannot access the properties beneath it.

There may be other options to fix this in your workflow, but a quick way would be a [JSON: Decode Node](https://docs.losant.com/workflows/logic/json-decode/) to parse that string as an object and put that back on the payload at the same path.