# Help with shell command to get a result in a node

**URL:** <https://discourse.nodered.org/t/help-with-shell-command-to-get-a-result-in-a-node/15548>\
**Category:** General\
**Created:** [15 September 2019 08:03 UTC](https://discourse.nodered.org/t/help-with-shell-command-to-get-a-result-in-a-node/15548 "2019-09-15T08:03:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [15 September 2019 08:31 UTC](https://discourse.nodered.org/t/help-with-shell-command-to-get-a-result-in-a-node/15548/5 "2019-09-15T08:31:04Z")

</div>

Yeah,

I think that is a layover from other problems parsing variables where sometimes it can't deal with something like `msg.payload`.

Or have I got that bit wrong too?  
(Sorry. Brain drain happening.)

---

_[View the full topic](https://discourse.nodered.org/t/help-with-shell-command-to-get-a-result-in-a-node/15548)._