Automations
How Kaer handles recurring tasks, schedules, and webhook-triggered work.
Automations are for work that should happen again without being rewritten from scratch each time. The page is built around operational ownership. You can see what is running, what is paused, what is failing, what it costs, and which definition needs attention next.
What belongs in an automation
A good automation is predictable. Daily monitors, weekly reports, scheduled summaries, recurring client updates, and inbound webhook actions all fit naturally here. If the work still changes shape every time you run it, keep it in Agent a bit longer. Once the pattern is stable, Automation is the right home.
How to read the page
The upper section helps you understand the operating temperature. The pulse view shows how often automations ran recently. The summary panel shows spend, burn rate, and whether any definitions are failing. Lower on the page, each automation card makes the details practical: status, next run, run history, rough cost profile, and quick controls.
When to pause instead of edit
If an automation is firing at the wrong time, using stale source data, or generating noisy output, pause it first. Pausing preserves the definition while giving you room to adjust the task, schedule, or alerting logic without producing more unwanted work in the meantime.
How this page relates to workflows
Automations are about repeatability and timing. Workflows are about visible sequence and structure. If the recurring work is still basically one task with a trigger, keep it here. If the process needs several distinct stages, branching logic, or clearer handoffs, move it into Workflows.