-
-
Notifications
You must be signed in to change notification settings - Fork 52
Scheduling
Naveen Raj edited this page Apr 11, 2026
·
1 revision
Automate agent and orchestration runs on a recurring schedule — no external cron setup needed.
Open Settings → Schedules and click New Schedule. Configure:
| Field | Description |
|---|---|
| Name | A label for this schedule |
| Agent / Orchestration | What to run when the schedule fires |
| Schedule Type | Interval or fixed-time cron |
| Prompt | Standing instruction sent to the agent each run |
| Messaging Channel | Where to post results (optional) |
Run every N minutes, hours, or days:
| Example | Meaning |
|---|---|
| Every 15 minutes | */15 * * * * |
| Every hour | 0 * * * * |
| Every 6 hours | 0 */6 * * * |
| Every day | 0 0 * * * |
Run at specific times using standard cron syntax:
┌─── minute (0–59)
│ ┌─── hour (0–23)
│ │ ┌─── day of month (1–31)
│ │ │ ┌─── month (1–12)
│ │ │ │ ┌─── day of week (0–6, Sun=0)
│ │ │ │ │
* * * * *
| Cron Expression | Meaning |
|---|---|
0 9 * * 1-5 |
Weekdays at 9 AM |
0 9 * * MON |
Every Monday at 9 AM |
30 8 1 * * |
1st of every month at 8:30 AM |
0 9,17 * * * |
Daily at 9 AM and 5 PM |
The Prompt field is what the agent receives each time the schedule fires — a standing instruction.
Examples:
- "Check our GitHub issues opened in the last 24 hours and summarize them in a morning report. Save to vault/reports/daily-issues.md"
- "Pull yesterday's sales data from the database and generate a performance summary. Post results to Slack."
- "Monitor the /status page of our API and alert if any endpoints return non-200."
If the scheduled agent has a connected messaging channel (Slack, Telegram, Discord, etc.), results are automatically sent to that channel after each run.
Setup:
- Configure a messaging channel for the agent — see Messaging Integration
- Create a schedule for that agent
- Results post automatically after each scheduled run
This is the primary way to get proactive agent updates without manually checking the UI.
- Enable / Disable — toggle without deleting the schedule
- Run Now — trigger an immediate one-off run
- Execution History — view logs for past runs in Settings → Logs
- Last Run / Next Run — shown in the schedule list
Schedule: 0 8 * * 1-5 (weekdays at 8 AM)
Prompt:
Prepare a morning standup report:
1. Check open GitHub PRs awaiting review
2. Summarize any new Jira tickets assigned to the team
3. Pull yesterday's deployment logs for any failures
4. Post a concise summary to the #standup Slack channel
Agent: Productivity Agent with GitHub, Jira, and Slack MCP servers connected.
- Agents — creating the agent to schedule
- Messaging Integration — connecting channels for result notifications
- Orchestration — scheduling multi-agent pipelines