Automations
Schedule skills and tasks as recurring SOPs your agents run on their own.
A Skill turns repeatable work into a reusable workflow. An Automation takes the next step: it runs that work on a schedule, without you asking each time. Set an agent to draft your morning briefing at 8am, sweep your inbox every hour, or post a weekly report — then review the results instead of doing the work.
Create an automation
The simplest way is to just ask an agent — the built-in Buda Automations Skill turns plain language into a schedule.
Tell an agent what to run, and when
In a session, say something like "Every weekday at 9am, summarize new support tickets and post them to the team channel." The agent recognizes the recurring phrasing and sets up the schedule.
Confirm the schedule
The agent reads back what it'll run and when. Each Automation has a name, the task (the prompt the agent runs), and a schedule. You can also manage them from the Scheduled Tasks view for an agent in a Space.
Choose where the output goes
Results can land back in a session, or notify a channel or session you pick — so a recurring report shows up where your team already works.
Schedules and triggers
An Automation runs on one of three schedule types:
| Type | What it does | Example |
|---|---|---|
| Interval | Repeats every N minutes. | Every 60 minutes |
| Cron | Repeats on a cron expression, with a timezone. | 0 9 * * 1-5 (weekdays at 9:00) |
| Once | Runs a single time at a future moment. | Tomorrow at 14:00 |
You can also cap total runs with a max-runs limit (leave it off for unlimited) and set the timezone so cron schedules fire at your local time.
Schedule limits depend on your plan: Free allows up to 5 Automations with a 120-minute minimum interval and no cron; Plus allows 20 (cron, 30-min minimum); Pro allows 100 (cron, 5-min minimum); Enterprise is unlimited (cron, 1-min minimum).
Monitoring runs
Each Automation keeps a run history. Every run records a status — pending, running, completed, failed, or skipped — along with start and finish times, and an error message if it failed. Buda also tracks the next scheduled run and a running run count, so you can see at a glance whether an Automation is healthy and when it last fired. A completed run links to the agent session it created, so you can open it and read exactly what the agent did.
Editing and pausing
- Pause — disable an Automation to stop it without deleting it; its next run is cleared until you re-enable it.
- Resume — re-enable it and Buda recalculates the next run time.
- Edit — change the name, task, schedule, timezone, or run cap.
- Delete — remove it entirely.
Automations are the scheduled half of Skills and automations. Pair a Skill (the how) with an Automation (the when) to run a full SOP unattended.