schedule

Use schedule_create with an expression in 5-field cron syntax (e.g. "0 9 * * 1-5" for weekdays at 9am) or an RRULE string with a required DTSTART line. The syntax is auto-detected, or you can set the syntax parameter explicitly.

Pass fire_at as an ISO 8601 timestamp with timezone offset instead of an expression. One-shot schedules fire once, are marked as fired, and are automatically disabled; they support both execute and notify modes.

Execute sends the message to the assistant for autonomous handling, notify pushes a notification to your channels, script runs a shell command directly without an LLM, and workflow runs a saved multi-agent workflow by name. Choose based on whether the task needs reasoning, a simple alert, deterministic commands, or a multi-step workflow.

Yes. Scripts can call "assistant notifications send" to alert you directly, or "assistant conversations wake" to hand off to the assistant when a condition is met. This keeps routine runs fast while escalating only noteworthy events.

Scheduled messages run without user interaction, so missing integrations cause silent failures. Check the integration status returned by schedule_create — email tasks need an email integration, calls need Twilio, and web tasks need browser automation.

Use task_list_add for "add to my tasks" or queue-style requests with no timing component. Schedules are only for deferred or recurring execution at specific times, not general task tracking.