# Sharing data (json) between Node-red Editor (Nodes) and custom editor theme comonents

**URL:** <https://discourse.nodered.org/t/sharing-data-json-between-node-red-editor-nodes-and-custom-editor-theme-comonents/81028>\
**Category:** General\
**Tags:** editor\
**Created:** [4 September 2023 08:27 UTC](https://discourse.nodered.org/t/sharing-data-json-between-node-red-editor-nodes-and-custom-editor-theme-comonents/81028 "2023-09-04T08:27:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 September 2023 08:47 UTC](https://discourse.nodered.org/t/sharing-data-json-between-node-red-editor-nodes-and-custom-editor-theme-comonents/81028/4 "2023-09-04T08:47:29Z")

</div>

> [@Pioneerj](#):
>
> After deploy/trigger I am having some result json in node

You will probably need to create a node-red plug-in to capture the "deploy" event. From there, you could store this "data" (whatever that is) in memory or file, ready for the client side request for it.

> [@Pioneerj](#):
>
> Now, this result json I want to access it from my custom editor theme component (js) file

To access this "data", you can request it (via http/AJAX) from client side to node-red. Here is an example: [Async getting list for node config - #4 by Steve-Mcl](https://discourse.nodered.org/t/async-getting-list-for-node-config/57506/4)  
This endpoint would typically be created in your plug-in.

---

_[View the full topic](https://discourse.nodered.org/t/sharing-data-json-between-node-red-editor-nodes-and-custom-editor-theme-comonents/81028)._