Alerts
Hear about it first. Not from a customer.
Alert rules watch every run for failures, error rates, slow runs, silence, your own events and budgets, and tell the right people in the app, by email or on a webhook.
The problem
Agents fail quietly.
A source starts blocking the agent and it writes half a report. A scheduled agent stops running and nothing raises an error, because nothing ran. The agent finishes, says something reasonable, and nobody notices for a week. An alert is how a problem reaches a person on the day it starts.
It failed.
It slowed down.
It went quiet.
Conditions
Match the alert to how the agent fails.
A rule watches one agent, or every agent in the workspace when you leave the agent blank. Pick the condition that fits: an agent that must never fail gets an alert on any failure; a busy agent where one failure is noise gets one on its error rate.
Any run fails.
Error rate exceeds threshold.
Run duration exceeds threshold.
Agent has no activity.
Custom event type observed.
order.failed, and the rule fires on it.Intelligence finding escalates.
Monthly budget exceeded.
Channels
Sent where someone will see it.
Every alert lands in the app, on the Notifications page, with an unread badge on the user menu. Add email for up to ten recipients, a webhook for your own systems, or both.
A webhook is a JSON POST with the rule, its condition and what triggered it: the run and its error, the observed error rate, or the spend against the budget. A delivery that fails is retried twice, a few minutes apart.
Without the noise
One alert, not twenty.
A quiet period after each alert.
Budgets once a month.
Tests stay out of it.
Free two-week pilot
Try it free for two weeks.
We set it up on one job your team repeats. You approve every email and post. If it does not work for you, you stop and pay nothing.
