Crons
List scheduled triggers (read-only)
Crons
Crons are scheduled triggers that automatically create tasks or fire events on a schedule. This endpoint is read-only — crons are defined and managed in OpenClaw, which is the source of truth for all scheduled operations.
Base URL: https://mission-control-ten.vercel.app/api/v1
GET /crons
List all crons configured for your organization.
curl https://mission-control-ten.vercel.app/api/v1/crons \
-H "Authorization: Bearer YOUR_API_KEY"Response
{
"ok": true,
"data": [
{
"id": "cron_abc123",
"name": "Daily standup tasks",
"schedule": "0 9 * * 1-5",
"action": "create_task",
"config": {
"title": "Daily standup",
"project_id": "proj_xyz789",
"status": "todo"
},
"enabled": true,
"org_id": "org_xyz789",
"created_at": "2024-01-10T09:00:00Z",
"last_run_at": "2024-01-20T09:00:00Z",
"next_run_at": "2024-01-21T09:00:00Z"
}
]
}GET /crons/:id
Fetch a single cron by ID.
curl https://mission-control-ten.vercel.app/api/v1/crons/cron_abc123 \
-H "Authorization: Bearer YOUR_API_KEY"Cron Object
| Field | Type | Description |
|---|---|---|
id | string | Unique cron identifier |
name | string | Display name |
schedule | string | Cron expression (e.g. 0 9 * * 1-5) |
action | string | What the cron does when it fires |
config | object | Action-specific configuration |
enabled | boolean | Whether this cron is currently active |
org_id | string | Organization this cron belongs to |
created_at | string | ISO 8601 creation timestamp |
last_run_at | string | null | When the cron last fired |
next_run_at | string | null | When the cron will next fire |
Why Read-Only?
Cron schedules are managed in OpenClaw, the scheduler that drives Mission Control's automation layer. OpenClaw owns the schedule definitions and syncs them to Mission Control — editing crons via the Mission Control API would conflict with OpenClaw's state.
To create or modify scheduled tasks, configure them in OpenClaw directly.
The cron model in the /agent command bus also reflects this — only read is supported for model: "cron".