# Payload result path after math

**URL:** <https://forums.losant.com/t/payload-result-path-after-math/1234>\
**Category:** Help\
**Created:** [November 9, 2018, 2:35pm UTC](https://forums.losant.com/t/payload-result-path-after-math/1234 "2018-11-09T14:35:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [November 9, 2018, 7:15pm UTC](https://forums.losant.com/t/payload-result-path-after-math/1234/2 "2018-11-09T19:15:38Z")

</div>

Hey Lars,

The workflow payload and data available on device attributes are separate structures. In order to move a value from the payload onto a device attribute, you’ll need to use a [Device State Node](https://docs.losant.com/workflows/outputs/device-state/) to record the data onto the desired device.

Here’s a related forum post with more details. The example in that post is using a workflow to convert Celsius to Fahrenheit.

> [@Simple device incoming data transformations](https://forums.losant.com/t/simple-device-incoming-data-transformations/1044):
>
> I have temp in C coming in from an OEM device that I sell services for. We’re US-based and need to graph temp in F on our dashboards. How do we do this? Thanks!

If you’re triggering the workflow from Device State, using a Device State output will cause the workflow to trigger again. The above link includes instructions for using a conditional node to prevent that loop.

---

_[View the full topic](https://forums.losant.com/t/payload-result-path-after-math/1234)._