# Feature request : Integrated Google Time Zone API

**URL:** https://forums.losant.com/t/feature-request-integrated-google-time-zone-api/972
**Category:** Help
**Created:** [June 5, 2018, 9:52pm UTC](https://forums.losant.com/t/feature-request-integrated-google-time-zone-api/972 "2018-06-05T21:52:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Steve\_Simpson1](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@Steve\_Simpson1](https://forums.losant.com/u/Steve_Simpson1)
#### Post date: [June 5, 2018, 9:52pm UTC](https://forums.losant.com/t/feature-request-integrated-google-time-zone-api/972/1 "2018-06-05T21:52:54Z")

</div>

Our application requires control over date-time formatting. In particular we want to be able to report date / time with respect to lat-long device coordinates. The classical approach is to use a time zone database, but these need to be regularly maintained and don’t really fit with Losant workflows. Google offers a RESTful Time Zone API, which can be accessed from an HTTP node.

What I’d like is a Time Zone workflow block that can be fed a UTC time and lat-long or TZ database names like “Pacific/Auckland” and which returns the time zone offset for that time and place.

I’d also like it to cleverly cache the results with the view that most lat-long values will be in the same time zone.