Create a scheduled task
create_scheduled_taskCreate a recurring agent mission. Firing it — on schedule, or immediately via run_scheduled_task — creates an ordinary tracker issue assigned to the agent, which drives a normal pipeline run: a scheduled task is a stored mission request, not a new execution mode. This tool calls the SHIP API, documented at https://letsship.ai/docs/api. Requires the config:write capability.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Scheduled task name, shown in the console and used in the issue title | |
| time | Yes | 24-hour wall-clock time in `timezone`, e.g. '09:00'. | |
| labels | No | Tracker label names put on every issue this scheduled task files (default none). The label must ALREADY exist in the project's tracker team — the platform attaches labels but cannot create them, so a name the workspace does not have is dropped. | |
| prompt | Yes | Becomes the created issue's description verbatim on every fire | |
| enabled | No | Whether the schedule is armed (default true) | |
| weekday | No | Day of week — required when interval is 'weekly'. | |
| interval | Yes | Fire cadence. 'weekly' requires weekday; 'monthly' requires dayOfMonth. | |
| timezone | Yes | IANA timezone id, e.g. 'Europe/Amsterdam'. | |
| projectId | Yes | Project id the scheduled task belongs to | |
| dayOfMonth | No | Day of month, 1-28 — required when interval is 'monthly' (capped at 28 so every month has the day). | |
| templateKey | No | Attribution only, when authored from a template — see list_scheduled_task_templates | |
| skipIfPreviousOpen | No | Skip a scheduled fire while the previous fire's mission is still open (default true — the guardrail is opt-out, not opt-in) |