Hello Gliders,
I’m running into a timezone issue where a UTC timestamp stored in Glide seems to arrive at my JavaScript column already converted — and incorrectly.
Setup
- Guests fill an external form and enter a check-in time (e.g. 15:00 Paris time)
- On validation, a webhook sends the data to Glide, which stores the check-in time as a UTC timestamp (13:00 UTC = 15:00 Paris, correct)
- The column is set to “Don’t respect timezone”
- A JavaScript column then receives that UTC value to convert it to Paris time for use in a Glide workflow
The problem
To debug, I logged the raw value received by the JS column:
return String(p1) + " | type:" + typeof p1;
Result:
2026-05-13T11:00:00.000Z | type:string
The column stores 2026-05-13T13:00:00.000Z (UTC), but the JS column receives 2026-05-13T11:00:00.000Z — which is 2 hours behind UTC (i.e. 11:00 UTC instead of 13:00 UTC). So by the time I try to convert to Paris time, I’m already starting from a wrong value.
Question
Why would Glide pass a different timestamp to the JS column than what’s stored? Could the “respect timezone” setting, or some implicit conversion happening at the JS column input level, explain this 2-hour discrepancy?
My end goal is to include the correct Paris local time in automated messages sent via Glide workflows.
Any insight would be greatly appreciated!
Thanks,
Lucas