schedule
Register a WhatsApp message to the account owner's own phone at a later time:
once (at), every every_s seconds, or on a cron schedule (give exactly one).
You cannot send it later yourself; tell the human the registered local time this
returns. A scheduled message usually arrives outside the 24h window, so it is
sent as a template and counts toward the monthly quota. The human can list and
cancel from WhatsApp too: schedules, cancel <name>.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"text": "<text>"
},
"name": "schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| at | No | One time: ISO 8601, e.g. 2026-11-14T09:00:00+01:00. Without an offset it is read in `timezone`. Must be in the future. | |
| cron | No | Repeat on a 5-field cron expression (minute hour day month weekday), read in `timezone`, e.g. "0 9 * * 1-5" = 09:00 on weekdays. Runs at least 15 minutes apart. | |
| name | No | Short name (letters, digits, . _ -; up to 40) the human can cancel it by from WhatsApp; default schedule-N. | |
| text | Yes | The message to send at each run (1-1024 characters), to the key owner's phone. | |
| buttons | No | Optional reply options (up to 3); the answer arrives later via `check_replies`. Nobody waits for it. | |
| every_s | No | Repeat every N seconds (at least 900, i.e. 15 minutes). | |
| timezone | No | IANA timezone, e.g. "Europe/Warsaw". Default: the phone country's zone (UTC when the country has several). Pass the human's zone when you know it. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |