schedules:manage. Creating or editing a schedule also needs events:write for an event action, or resources:write for a resource action.
Try it
This example publishes a reminder every hour:What you’ll see
The response includes id, name, enabled, action and the next run time.- intervalSeconds repeats every 60 seconds to one year.
- runAt schedules one future time instead. Use an ISO timestamp with a timezone, such as
2027-01-01T09:00:00-05:00. - enabled is
trueby default. Set it tofalseto pause.
runAt or intervalSeconds, not both. Run history is included when you read a schedule.
Available actions
For example, this action turns an AlexWeb switch on:
Other requests
A completed run creates a
schedule.executed event. Schedules survive restarts. After downtime, a repeating schedule runs once and moves to its next interval instead of replaying every missed run.
Actions stop when the credential that authorized the schedule is revoked or expires. For OAuth, the connection’s grant lifetime applies.