This page covers three Web UI screens that handle outbound automation and admin
alerts: Notifications, Webhooks and Schedules.
Notifications
The “Notifications” screen has three parts:
Inbox — an event feed with filters by category, severity (info / warning /
critical) and “unread only”. Clicking an item marks it read and deep-links to
its tab; there is “Mark all read”.
Delivery matrix — rows: event categories (groups with expandable events),
columns: channels (Web UI, e-mail, Telegram, push). Each cell is a checkbox; you
can set a rule per group or per event. “Important” groups are always on for the
Web UI. Inactive channels are disabled with a setup hint.
Telegram linking — a list of linked chats (label, blocked badge, “Unlink”)
and a “Link” button via deep link. The e-mail channel needs verification
(the “Community” screen).
Webhooks
The “Webhooks” screen is outbound HTTP notifications. “+ Create”: a URL and
event checkboxes (multi-select; an empty selection is rejected,
turn.completed is pre-checked). Rows show the URL and subscribed events, with
search and sorting. The event kind is sent in the X-AIHummer-Event header.
This page covers three Web UI screens that handle outbound automation and admin
alerts: **Notifications**, **Webhooks** and **Schedules**.
## Notifications
The **"Notifications"** screen has three parts:
- **Inbox** — an event feed with filters by category, severity (info / warning /
critical) and "unread only". Clicking an item marks it read and deep-links to
its tab; there is "Mark all read".
- **Delivery matrix** — rows: event categories (groups with expandable events),
columns: channels (Web UI, e-mail, Telegram, push). Each cell is a checkbox; you
can set a rule per group or per event. "Important" groups are always on for the
Web UI. Inactive channels are disabled with a setup hint.
- **Telegram linking** — a list of linked chats (label, blocked badge, "Unlink")
and a **"Link"** button via deep link. The e-mail channel needs verification
(the "Community" screen).
## Webhooks
The **"Webhooks"** screen is outbound HTTP notifications. "+ Create": a URL and
**event checkboxes** (multi-select; an empty selection is rejected,
`turn.completed` is pre-checked). Rows show the URL and subscribed events, with
search and sorting. The event kind is sent in the `X-AIHummer-Event` header.
**20 event kinds** are available:
| Group | Events |
|---|---|
| Turns & messages | `turn.completed`, `turn.failed`, `message.created`, `conversation.created` |
| Agents | `agent.created`, `agent.updated`, `agent.deleted` |
| Plugins & channels | `plugin.installed`, `plugin.removed`, `channel.added`, `channel.removed` |
| Workspaces | `workspace.created` |
| Schedules | `schedule.created`, `schedule.updated`, `schedule.deleted`, `schedule.fired` |
| Approvals | `approval.requested`, `approval.resolved` |
| Memory | `memory.stored`, `memory.captured` |
## Schedules
The **"Schedules"** screen is the task scheduler: a table (task, agent, channel,
cron, next run, status) with pause/resume, edit and delete. "+ Create":
- **Kind**: `repeating` (a cron expression, e.g. `0 9 * * *`), `once` (a
date/time) or `reminder`.
- **Target agent** and **prompt** (what exactly is sent), **target channel**
(where the reply goes). Advanced: a raw JSON payload override.
This is how you build scheduled actions: "every weekday at 9:00 agent X posts the
result of prompt Z into channel Y".
## Next
- [Channels](/en/v1.0/webui/channels) — where messages and alerts go.
- [Inbound triggers](/en/v1.0/api/inbound-triggers) — webhooks in the API context.
- [Observability](/en/v1.0/operations/observability) — which events matter.
