schedules.yaml and can be listed, run manually, or executed automatically in daemon mode.
Commands
agenticai schedule list
List all configured schedules fromschedules.yaml.
agenticai schedule run
Run a specific schedule immediately (useful for testing).Arguments
Name of the schedule to run (as defined in
schedules.yaml)Example:Options
Public webhook base URL for Twilio callbacksShort form:
-wRequired: YesExample:Schedule Configuration
Schedules are defined inschedules.yaml:
Cron Format
0 9 * * *- Daily at 9:00 AM0 14 * * 1-5- Weekdays at 2:00 PM*/15 * * * *- Every 15 minutes0 0 1 * *- First day of every month at midnight0 17 * * 5- Every Friday at 5:00 PM
Examples
List All Schedules
schedules.yaml, including disabled ones.
Run Schedule Immediately
Test a schedule before enabling it:Run in Daemon Mode
For automatic execution, use daemon mode:Workflow
Development
-
Create schedule in
schedules.yaml: -
Test manually:
-
Enable and run in daemon:
Production
-
Install service:
-
Verify schedules:
-
Monitor logs:
Schedule Metadata
Each call can include metadata for tracking:- Logged in server logs
- Sent to OpenClaw Gateway
- Included in Telegram notifications
- Available in Twilio call records
Error Handling
Schedule Not Found
Error:Invalid Cron Expression
Error:schedules.yaml. Use crontab.guru to validate.
Missing Webhook URL
Error:No Calls Defined
If a schedule has an emptycalls array, it runs but does nothing:
Schedule Management Tips
Testing New Schedules
- Set
enabled: falseinitially - Run manually with
schedule run - Verify call behavior
- Enable and deploy
Bulk Calls
Schedules support multiple calls:Time Zones
Cron times are based on the server’s system time. For consistent scheduling:See Also
- Server Command - Start the webhook server
- Daemon Mode - Run server with scheduler
- Service Commands - Background service management
- Trigger Command - Manual call triggering