Complete guide to using Nylas CLI's offline timezone tools for global team coordination, DST management, and meeting scheduling.
⚡ Key Feature: All timezone commands work 100% offline—no API access required. Perfect for remote teams, travel planning, and scheduling across time zones.
Nylas CLI includes powerful timezone utilities that solve common challenges faced by global teams:
- 83% of professionals struggle with scheduling across time zones
- DST changes cause confusion and missed meetings
- Finding overlapping working hours is time-consuming and error-prone
| Feature | Benefit |
|---|---|
| 100% Offline | Works on planes, trains, anywhere without WiFi |
| Instant Results | No network latency, calculations are local |
| Privacy-First | No data sent to external servers |
| No Rate Limits | Use as frequently as needed |
| Free Forever | No API costs or subscription fees |
The CLI understands common timezone abbreviations for faster typing:
| Abbreviation | Full IANA Name |
|---|---|
| PST/PDT | America/Los_Angeles |
| EST/EDT | America/New_York |
| CST/CDT | America/Chicago |
| MST/MDT | America/Denver |
| GMT/BST | Europe/London |
| IST | Asia/Kolkata |
| JST | Asia/Tokyo |
| AEST/AEDT | Australia/Sydney |
# Convert current time from PST to IST
nylas timezone convert --from PST --to IST
# Convert specific time
nylas timezone convert \
--from UTC \
--to America/New_York \
--time "2025-01-01T12:00:00Z"# Check DST for New York in 2026
nylas timezone dst --zone America/New_York --year 2026# Find overlapping times for 3 zones
nylas timezone find-meeting \
--zones "America/New_York,Europe/London,Asia/Tokyo"# Get info about a timezone
nylas timezone info UTC
# List all American timezones
nylas timezone list --filter AmericaConvert time from one timezone to another with automatic DST handling.
nylas timezone convert --from <zone> --to <zone> # Convert current time
nylas timezone convert --from <zone> --to <zone> --time <RFC3339> # Convert specific time
nylas timezone convert --from <zone> --to <zone> --json # JSON output--from(required) - Source time zone (IANA name or abbreviation)--to(required) - Target time zone (IANA name or abbreviation)--time- Specific time to convert (RFC3339 format: 2025-01-01T12:00:00Z)--json- Output as JSON
# Convert current time
nylas timezone convert --from PST --to IST
# Convert specific time
nylas timezone convert --from UTC --to America/New_York --time "2025-01-01T12:00:00Z"
# JSON output
nylas timezone convert --from UTC --to EST --jsonFind overlapping working hours across multiple time zones for scheduling meetings.
nylas timezone find-meeting --zones <zones> # Basic meeting finder
nylas timezone find-meeting --zones <zones> --duration <duration> # Specify duration
nylas timezone find-meeting --zones <zones> --start-hour <HH:MM> --end-hour <HH:MM> # Custom hours
nylas timezone find-meeting --zones <zones> --exclude-weekends # Skip weekends--zones(required) - Comma-separated list of time zones--duration- Meeting duration (default: 1h). Format: 30m, 1h, 1h30m--start-hour- Working hours start (default: 09:00). Format: HH:MM--end-hour- Working hours end (default: 17:00). Format: HH:MM--start-date- Search start date (default: today). Format: YYYY-MM-DD--end-date- Search end date (default: 7 days from start). Format: YYYY-MM-DD--exclude-weekends- Skip Saturday and Sunday--json- Output as JSON
# Basic meeting finder
nylas timezone find-meeting --zones "America/New_York,Europe/London,Asia/Tokyo"
# Custom working hours
nylas timezone find-meeting --zones "PST,EST,IST" --duration 30m \
--start-hour 10:00 --end-hour 16:00 --exclude-weekends
# Specific date range
nylas timezone find-meeting --zones "America/Los_Angeles,Europe/Paris" \
--start-date 2026-01-15 --end-date 2026-01-22Note: Meeting finder algorithm is planned but not yet implemented.
Display Daylight Saving Time transitions for a specific time zone and year.
nylas timezone dst --zone <zone> # Check current year
nylas timezone dst --zone <zone> --year <year> # Check specific year
nylas timezone dst --zone <zone> --json # JSON output--zone(required) - Time zone to check (IANA name or abbreviation)--year- Year to check (default: current year)--json- Output as JSON
# Check DST for a zone
nylas timezone dst --zone America/New_York --year 2026
# Zone without DST
nylas timezone dst --zone America/Phoenix
# Using abbreviation
nylas timezone dst --zone PST
# JSON output
nylas timezone dst --zone EST --jsonDisplay all IANA time zones with current time and offset information.
nylas timezone list # List all zones
nylas timezone list --filter <text> # Filter by name
nylas timezone list --json # JSON output--filter- Filter zones by name (case-insensitive)--json- Output as JSON
# List all zones (593 total)
nylas timezone list
# Filter by region
nylas timezone list --filter America
# Filter by city
nylas timezone list --filter Tokyo
# JSON output
nylas timezone list --filter UTC --jsonDisplay detailed information about a specific time zone.
nylas timezone info <zone> # Get info for zone
nylas timezone info --zone <zone> # Alternative syntax
nylas timezone info --zone <zone> --time <RFC3339> # Info at specific time
nylas timezone info --zone <zone> --json # JSON output--zone- Time zone to query (IANA name or abbreviation)--time- Check info at specific time (RFC3339 format)--json- Output as JSON
Note: Zone can be provided as a positional argument or via
--zoneflag.
# Get zone information
nylas timezone info America/New_York
# Using abbreviation
nylas timezone info PST
# Zone without DST
nylas timezone info Asia/Tokyo
# Check at specific time
nylas timezone info --zone America/New_York --time "2026-07-01T12:00:00Z"
# JSON output
nylas timezone info UTC --json- Use abbreviations -
PSTinstead ofAmerica/Los_Angeles - JSON for scripting -
nylas timezone info UTC --json | jq '.offset_seconds' - Check multiple zones - Loop through zones in bash scripts
- Plan for DST - Check transitions before scheduling recurring meetings
- Save aliases - Add common conversions to
~/.bashrcor~/.zshrc - Works offline - No WiFi needed, all calculations are local
- Remote team coordination - Convert standup times across timezones
- Client calls - Check if it's business hours before calling
- Travel planning - Convert flight times to local timezone
- Meeting scheduling - Find overlapping working hours globally
- DST awareness - Check transitions before scheduling recurring meetings
- Multi-region deployments - Convert deployment times to all datacenter regions
See Calendar Integration for timezone support in calendar commands.
$ nylas timezone info Invalid/Zone
Error: get time zone info: unknown time zone Invalid/Zone
# Solution: Use list to find valid zones
nylas timezone list --filter <search>$ nylas timezone convert --from UTC --to EST --time "invalid"
Error: invalid time format (use RFC3339, e.g., 2025-01-01T12:00:00Z)
# Solution: Use RFC3339 format
# YYYY-MM-DDTHH:MM:SSZ (UTC)
# YYYY-MM-DDTHH:MM:SS±HH:MM (with offset)$ nylas timezone convert --from PST
Error: required flag(s) "to" not set
# Solution: Both --from and --to are required
nylas timezone convert --from PST --to EST# If abbreviation isn't in the built-in list, use full IANA name
nylas timezone list --filter <region>
# Then use the full name from the list- Instant execution - All operations are local calculations
- No network calls - Works 100% offline
- No rate limits - Use as frequently as needed
- Privacy-first - No data ever sent to external servers
- Minimal resources - Uses OS timezone database
Convert calendar events to any timezone using --timezone and --show-tz flags:
# List events in a specific timezone
nylas calendar events list --timezone America/Los_Angeles
# Show timezone information for events
nylas calendar events list --show-tz
# View specific event in different timezone
nylas calendar events show <event-id> --timezone Europe/LondonAuto-detection: Commands use your system timezone by default.
Calendar commands automatically warn about events scheduled near or during DST transitions:
- ⛔ Error - Time doesn't exist (spring forward gap)
⚠️ Warning - DST transition within 7 days- ℹ️ Info - Time occurs twice (fall back)
Configure working hours and break periods in ~/.nylas/config.yaml to prevent scheduling conflicts:
working_hours:
default:
enabled: true
start: "09:00"
end: "17:00"
breaks:
- name: "Lunch"
start: "12:00"
end: "13:00"
type: "lunch" # lunch, coffee, or customBreak Types: lunch, coffee, custom
Enforcement:
- Working Hours - Soft warning (can override)
- Breaks - Hard block (cannot override, protects your break time)
See Calendar Commands for detailed configuration examples.
Parser supports: "in 2 hours", "tomorrow at 3pm", "next Tuesday 2pm", "Dec 25 10:00 AM", ISO formats. Integration with event creation is planned.
Timezone Locking (Planned): Lock events to specific timezone for in-person meetings.
- Command Reference - Quick command reference with examples
- AI Features - AI-powered scheduling and timezone-aware features
- Calendar Guide - Calendar events with timezone support
- TUI Guide - Interactive terminal interface
A: No! All timezone commands work 100% offline without any API access.
A: DST information comes from your operating system's timezone database, which is regularly updated. For most recent years, it's highly accurate.
A: The CLI supports common abbreviations (PST, EST, IST, etc.). For other zones, use the full IANA name from nylas timezone list.
A: Yes! Timezone commands work on macOS, Linux, and Windows.
A: Absolutely! Use the --json flag for machine-readable output that's easy to parse with tools like jq.
A: The meeting finder algorithm is planned but not yet implemented. The CLI and service interfaces are complete and ready for the algorithm.
Last Updated: December 21, 2025 Version: 1.0 Maintained By: Nylas CLI Team