Problem
Schedules can only be managed in Apify Console. Neither the CLI nor the MCP server exposes them, so a scripted or agent-driven workflow can create, push, and run an Actor, but cannot put it on a schedule without a human opening Console.
What we want
An apify schedules command group covering schedule CRUD.
Requirements
P0
- List schedules with their cron expression, timezone, and enabled state.
- Create a schedule for an Actor or a task, with cron expression and timezone.
- Delete a schedule.
P1
- Update an existing schedule.
- Enable and disable a schedule.
--json output for scripting.
Open questions
- Do schedules belong in the project config (declared in a file, applied on push), or flags only?
- Same surface in the MCP server, or CLI first?
Links
Problem
Schedules can only be managed in Apify Console. Neither the CLI nor the MCP server exposes them, so a scripted or agent-driven workflow can create, push, and run an Actor, but cannot put it on a schedule without a human opening Console.
What we want
An
apify schedulescommand group covering schedule CRUD.Requirements
P0
P1
--jsonoutput for scripting.Open questions
Links