Currently, converting a client's booking time to an internal team's timezone (e.g., EST to Nepal Time) requires complex JavaScript. Standard Date/Time formatters often fail or produce "Parsing Errors" when handling regional suffixes like "th" or "st," making internal Slack notifications unreliable for global teams.
Proposed Solution:
  1. Add a native "Timezone Converter" action in Workflows. It should allow users to:
  2. Select a source Date/Time variable.
  3. Select a target Timezone (e.g., Asia/Kathmandu).
  4. Output a clean custom value for use in notifications.
Why it matters:
Global agencies shouldn't have to write code just to tell their team what time a meeting starts in their local time. This would make GHL much more "user-friendly" for international operations.

Photo Viewer

View photos in a modal