Skip to main content
GHL MCP Guide
TZN

Timezone Handler

Location & Config · Basic · Updated March 2026

Retrieve the list of supported timezones for location configuration, ensuring accurate scheduling, appointment booking, and campaign delivery timing.

The Timezone Handler is a utility endpoint that returns all supported timezone identifiers for GHL location configuration. Simple but critical — every appointment, every scheduled message, every campaign delivery depends on the location having the correct timezone set.

What This MCP Tool Does

This tool retrieves the complete list of IANA timezone identifiers that GHL supports. When you are provisioning new sub-accounts programmatically or auditing existing location configurations, this endpoint tells you exactly which timezone values are valid. No guessing, no hardcoding timezone strings that might not be recognized.

Endpoint Reference

List supported timezones: GET /locations/timezones Returns an array of valid IANA timezone identifiers (e.g., America/New_York, America/Chicago, US/Pacific, Europe/London).

Authentication

Requires a Private Integration Token (PIT) with the locations scope enabled.

Key Parameters

This is a simple GET request with no required parameters. The response is an array of timezone strings.

Common timezone values for US-based agencies:

  • America/New_York — Eastern
  • America/Chicago — Central
  • America/Denver — Mountain
  • America/Los_Angeles — Pacific
  • Pacific/Honolulu — Hawaii

Important Notes

Always use this endpoint to validate timezone values before assigning them to locations via the Location CRUD tool. Passing an unrecognized timezone string will cause location creation or updates to fail.

Timezone affects everything downstream: calendar availability windows, appointment reminders, SMS delivery timing for scheduled messages, and campaign send times. A location set to the wrong timezone will have booking slots off by hours.

When provisioning sub-accounts for clients across multiple time zones, pull this list once and cache it. It does not change frequently.

Common Questions

Does the timezone affect when workflows execute? Yes. Workflow wait steps that use “time of day” conditions reference the location’s timezone. A workflow set to send at 9:00 AM will send at 9:00 AM in whatever timezone the location is configured for.

Can I change a location’s timezone after it has been set? Yes, through the Location CRUD update endpoint. However, changing the timezone on an active location will shift all scheduled events. Existing appointments retain their original times but will display differently.

What format are the timezone strings in? Standard IANA timezone identifiers as used in most programming languages and databases. These are the same strings you would use in JavaScript’s Intl.DateTimeFormat or Python’s pytz library.

Back to GHL MCP Guide