# The Payload Path Less Traveled By

**URL:** <https://forums.losant.com/t/the-payload-path-less-traveled-by/2101>\
**Category:** Losant Tips\
**Tags:** workflow, tips\
**Created:** [August 20, 2019, 2:45pm UTC](https://forums.losant.com/t/the-payload-path-less-traveled-by/2101 "2019-08-20T14:45:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\
**Post date:** [August 20, 2019, 2:45pm UTC](https://forums.losant.com/t/the-payload-path-less-traveled-by/2101/1 "2019-08-20T14:45:54Z")

</div>

The [Debug Node](https://docs.losant.com/workflows/outputs/debug/) truly is the Node I use the most, but every day I am still learning its hidden features. Today’s Tuesday Tip is a quick shortcut that may save you some time and effort as you build workflows.

Data is stored on the payload as a JSON object, and often contains nested data. Right-clicking on a value in the debug log will allow you to easily copy its path and use it within your workflow:

 ![38](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/0/06b5d9ce7e70afa2547841070e4af17572dd8713.gif)

This feature is especially useful for nested objects and arrays, and might even save you enough time to read some Robert Frost poems.

Thanks for stopping by our [Tuesday Tip](https://forums.losant.com/c/losant-tips), let us know if you have a tip you find useful or are looking for more. In the meantime, keep exploring!