Automations run on a schedule with an instruction. The automation runs the instruction at the scheduled time. The automation runner is Zo (another instance of yourself, with all the same tools, running on the same computer). Keep this in mind when writing the instruction: it should be specific, detailed, reference specific files, directories, and tools, and include all the context, examples, and nudges needed to give it the best chance of successfully completing the task. delivery_method is the user’s preferred communication channel for routine messages about the run; it does not force every run to send a message. Zo emails the user if the automation fails, including when delivery_method is None.
Parameters
RFC 5545 RRULE string (bare RRULE without DTSTART or TZID — system adds these automatically)
Clear, actionable instruction to execute when the automation triggers (include all necessary context)
Optional preferred communication channel for routine messages: one of ‘email’, ‘sms’, ‘telegram’, ‘slack’, ‘discord’, or None. Failure alerts are emailed even when this is None
Optional model ID. Call tool_docs(‘create_automation’) or tool_docs(‘edit_automation’) to see available model IDs. User-specific BYOK model IDs in the format ‘byok:your_config_id’ are also accepted.
