cron_create
Create a scheduled trigger. Schedule is a 5-field cron expression (minute hour dom month dow). It uses UTC by default; an IANA timezone such as America/Los_Angeles gives local wall-clock scheduling with daylight-saving changes handled automatically. Each fire dispatches a job to your handler (at-least-once delivery, so handlers are idempotent). Missed fires during platform downtime are NOT replayed.
Common patterns:
Pattern | Schedule |
Every 15 minutes |
|
Daily at 08:00 UTC |
|
Every 6 hours |
|
Weekly Monday midnight |
|
Minimum interval. Your plan sets the smallest gap allowed between two
fires. cron_list({ project_id }) reports it as
policy.min_interval_minutes, alongside policy.max_per_project. A
schedule tighter than the floor is refused with
CRON_SCHEDULE_TOO_FREQUENT and the message names both intervals.
Schedules that already exist are never re-checked — they keep firing on the
cadence they were created with.
Example:
{
"project_id": "my-saas",
"name": "daily-digest",
"schedule": "0 8 * * *",
"handler": "https://my-saas.somewhere.site/api/cron/daily-digest",
"payload": { "type": "digest" }
}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": {
"project_id": "<project_id>",
"schedule": "<schedule>",
"handler": "<handler>"
},
"name": "cron_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Optional display name, shown in the dashboard. | |
| enabled | No | Optional. Whether the trigger should fire. Defaults to true. | |
| handler | Yes | Project-relative /api path or full https:// URL the platform POSTs to on each fire. | |
| payload | No | Optional JSON object or JSON string — becomes the POST body on each fire. | |
| schedule | Yes | 5-field cron expression in the selected timezone (UTC when omitted). Must not fire more often than the plan floor reported by cron_list. | |
| timezone | No | Optional IANA timezone, e.g. America/Los_Angeles. Defaults to UTC; daylight-saving transitions are handled by the scheduler. | |
| project_id | Yes | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |