# Export device state to CSV \> FTP

**URL:** <https://forums.losant.com/t/export-device-state-to-csv-ftp/1559>\
**Category:** Help\
**Tags:** ftp, csv\
**Created:** [February 26, 2019, 9:19pm UTC](https://forums.losant.com/t/export-device-state-to-csv-ftp/1559 "2019-02-26T21:19:08Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\
**Post date:** [July 31, 2019, 2:29pm UTC](https://forums.losant.com/t/export-device-state-to-csv-ftp/1559/15 "2019-07-31T14:29:36Z")

</div>

Hi @paul_wareham,

I think the best solution would be to leverage a third-party to perform the conversion. Here are some options I can think of:

1. Cloud Functions: All of the cloud vendors (Google Cloud, AWS, Azure) support the ability to write serverless functions. This would allow you to create a small function that’s triggered by the workflow engine to communicate with FTP.

2. Roll your own API: Because you can trigger any arbitrary HTTP endpoint in the Workflow Engine, you can create your own microservice that takes CSV data as input and communicates to your FTP Server.

I’m happy to provide more thoughts here if needed!

---

_[View the full topic](https://forums.losant.com/t/export-device-state-to-csv-ftp/1559)._