# Time Zone Converter and Meeting Overlap Finder (`firebrick_zamia/timezone-meeting-planner`) Actor

Convert a date and time to many IANA time zones with DST handling and day shifts, or find shared working-hours windows across time zones for a given day. Pure compute, no network.

- **URL**: https://apify.com/firebrick_zamia/timezone-meeting-planner.md
- **Developed by:** [Aadam Ahmed](https://apify.com/firebrick_zamia) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Time Zone Converter and Meeting Overlap Finder

Convert a date and time into many time zones with correct daylight-saving handling, or find the windows when everyone is inside working hours. **No web calls, no AI**: it uses the IANA time zone database built into the Node.js runtime. Callable by developers and by AI agents through Apify's MCP server (https://mcp.apify.com).

- **convert**: for each target zone, the local time with offset, abbreviation, weekday, DST flag and the **day shift** versus the source (so "tomorrow" is never missed). Accepts a local time in a source zone (`2026-11-03T15:00` + `Asia/Dubai`) or an exact instant (`2026-11-03T11:00:00Z`).
- **overlap**: for a calendar day (read in the first zone of your list), the 30-minute-granular windows where **every** zone is within working hours, with local start and end per zone. Handles half-hour and 45-minute zones (India, Nepal) and DST differences between regions.

### Input

| Field | Meaning |
|---|---|
| `mode` | `convert` (default) or `overlap` |
| `dateTime`, `fromTimeZone` | convert: the moment and its zone |
| `timeZones` | IANA names such as `Asia/Dubai`, up to 50 |
| `date`, `workdayStart`, `workdayEnd`, `minMeetingMinutes`, `weekdaysOnly` | overlap options |

### Output example

Real output for `2026-11-03T15:00` in `Asia/Dubai` converted to `America/New_York`:

```json
{
  "kind": "conversion", "input": "2026-11-03T15:00", "source_time_zone": "Asia/Dubai",
  "utc": "2026-11-03T11:00:00.000Z", "time_zone": "America/New_York",
  "local_time": "2026-11-03T06:00:00-05:00", "utc_offset": "-05:00", "abbreviation": "EST",
  "weekday": "Tuesday", "is_dst": false, "day_shift_vs_source": 0,
  "ambiguous_source_time": false, "warning": null, "error": null
}
```

Overlap for Dubai and London on Mon 12 Jan 2026, 09:00-17:00 each: one window, 09:00-13:00 UTC, which is 13:00-17:00 in Dubai and 09:00-13:00 in London.

### Important limits (read before relying on it)

- **Daylight-saving edge cases are reported, not hidden.** A local time that does not exist (a spring-forward gap, such as 02:30 on 8 Mar 2026 in New York) returns an error. A local time that occurs twice (fall-back) uses the **earlier** instant and sets `ambiguous_source_time` with a warning.
- **Accuracy depends on the time zone data in the runtime** (Node.js with ICU / IANA tz data, https://www.iana.org/time-zones). Governments change rules at short notice; very recent or future rule changes may be missing until the runtime updates. Dates far in the future follow the current rules.
- Overlap uses **Monday to Friday** everywhere when `weekdaysOnly` is on. It does **not** know regional weekends (for example Friday-Saturday), public holidays, lunch breaks or individual calendars. One working-hours range applies to all zones.
- Overlap works in 30-minute steps on one calendar day of the first zone, so a window that crosses midnight of that zone is cut at the day boundary.
- `abbreviation` is whatever the runtime prints in US English; many zones show forms like `GMT+4` rather than a named abbreviation.

### Pricing (pay-per-event)

Uses Apify's built-in `apify-default-dataset-item` event: each zone conversion, or each overlap report, is one result. The owner sets the price in Apify Console. Suggested: **USD 2.00 per 1,000 results**. No priced direct competitor was found; the nearest are an MCP time server and a thin wrapper (see `apify/RESEARCH-3.md`).

### FAQ

**Does it call a website?** No.

**Can I convert many moments at once?** One moment per run in this version; a run can fan out to up to 50 zones.

**Does it support Windows time zone names?** No, IANA names only.

# Actor input Schema

## `mode` (type: `string`):

convert: show one moment in every listed time zone. overlap: find windows on a day when everybody is inside working hours.

## `dateTime` (type: `string`):

Mode convert. Local time in the source zone such as 2026-11-03T15:00, or an exact instant with an offset such as 2026-11-03T11:00:00Z.

## `fromTimeZone` (type: `string`):

Mode convert. IANA name of the zone the local date and time is in, for example Asia/Dubai. Ignored when dateTime carries its own offset.

## `timeZones` (type: `array`):

IANA names, one per line, for example America/New_York. In overlap mode the calendar day is read in the first zone (up to 50 zones).

## `date` (type: `string`):

Mode overlap. Calendar day YYYY-MM-DD, read in the first time zone of the list.

## `workdayStart` (type: `string`):

Mode overlap. Start of working hours in every zone, HH:MM.

## `workdayEnd` (type: `string`):

Mode overlap. End of working hours in every zone, HH:MM.

## `minMeetingMinutes` (type: `integer`):

Mode overlap. Only report windows at least this many minutes long (30 minute steps).

## `weekdaysOnly` (type: `boolean`):

Mode overlap. Skip slots that fall on a Saturday or Sunday in any zone. This uses Monday to Friday everywhere; it does not know regional weekends or holidays.

## Actor input object example

```json
{
  "mode": "convert",
  "dateTime": "2026-11-03T15:00",
  "fromTimeZone": "Asia/Dubai",
  "timeZones": [
    "America/New_York",
    "Europe/London",
    "Asia/Kolkata"
  ],
  "workdayStart": "09:00",
  "workdayEnd": "17:00",
  "minMeetingMinutes": 30,
  "weekdaysOnly": true
}
```

# Actor output Schema

## `results` (type: `string`):

All result records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "dateTime": "2026-11-03T15:00",
    "fromTimeZone": "Asia/Dubai",
    "timeZones": [
        "America/New_York",
        "Europe/London",
        "Asia/Kolkata"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("firebrick_zamia/timezone-meeting-planner").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "dateTime": "2026-11-03T15:00",
    "fromTimeZone": "Asia/Dubai",
    "timeZones": [
        "America/New_York",
        "Europe/London",
        "Asia/Kolkata",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("firebrick_zamia/timezone-meeting-planner").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "dateTime": "2026-11-03T15:00",
  "fromTimeZone": "Asia/Dubai",
  "timeZones": [
    "America/New_York",
    "Europe/London",
    "Asia/Kolkata"
  ]
}' |
apify call firebrick_zamia/timezone-meeting-planner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,firebrick_zamia/timezone-meeting-planner"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/wNznCTTHDkIOOBuuI/builds/XJpqPaE5QPHEyRWye/openapi.json