Appointment ISO DateTime Format should contain Timezone Information
M
Mark Kalnitski
Now the appointment format, when transmitted over the Webhook, looks like this:
2024-08-30T11:00
while it's taking the business location time zone as settings (mine is +02:00).
However, in all other softwares
2024-08-30T11:00 as default means
2024-08-30T11:00Z or
2024-08-30T13:00+02:00
So instead GHL should display the DateTime like this:
2024-08-30T11:00+02:00
because it's really messy to fix the datetime format in third party tools, especially when the GET and POST Appointment API of GHL actually returns the correct format and in this example 11am and 1pm are constantly overwriting each other.
Log In
S
Shreyas Birajdar
Merged in a post:
Workflow Trigger - Appointments - Timezone Aware Timestamp
W
Winston Brown
Appointment times are currently timezone unaware and represent a non-standard timestamp. {{appointment.start_time}} The {{appointment.timezone}} sends a timezone unaware three letter abbreviation "CST", "CDT", "PST", "PDT"; however, there are multiple timezones marked PST 1. Pacific Standard Time 2. Philippine Standard Time 3. Pakistan Standard Time .
Current timestamp format :
- {{appointment.start_time}} = "Friday, January 24, 2025 8:00 AM"
Current timestamp format :
- Digits -12 : 12
- Three letter abbreviations "CST", etc.
~ Abbreviations are not locale aware - e.g. multiple "PST" representations
A timezone aware ISO 3601 e.g. "2025-01-23T12:30:00-05:00" is needed to coordinate appointment times, correctly.