Win11 Toast Sink
The Win11 Toast sink shows a Windows 11 desktop notification for each matching event. It is a debugging tool — use it to quickly verify that events are flowing through the pipeline and that your matching rules work correctly.
This sink is local-only and best-effort. It is not a durable delivery mechanism and should not be used in production. For actual event delivery, use the Webhook, HTTP Pull, or SSE sinks.
Getting Started
Add a Win11 Toast sink to your config.yaml:
sink:
desktop_debug:
type: win11toastEach matching event will produce a Windows notification where the title is the event_type and the body is a best-effort summary of the data payload.
Platform Support
This sink is only available on Windows.
- On Windows 11, it uses the native notification system.
- On other platforms (Linux, macOS), the sink will automatically disable itself and log a warning at startup.
Installation of the required win11toast package is handled automatically on Windows systems via environment markers. No extra steps are needed.
Configuration
Minimal Configuration
sink:
desktop_debug:
type: win11toastDefaults: match: "*", max_body_length: 220.
Full Configuration
sink:
calendar_alerts:
type: win11toast
match:
- "google.calendar.*"
- "gmail.message_received"
max_body_length: 300Configuration Reference
| Parameter | Type | Default | Description |
|---|---|---|---|
type | string | — | Must be win11toast. |
match | string|list | "*" | Event type filter. Supports "*", "prefix.*", and exact matches. |
max_body_length | int | 220 | Maximum notification body length before truncation. |
How the Notification Body is Built
The sink tries to extract meaningful fields from the event data in this order:
- Looks for well-known keys:
summary,title,subject,name,filename,message,description,snippet,status,action. - Falls back to extracting scalar values from nested JSON.
- Falls back to a truncated JSON snippet.
The body is prefixed with entity={entity_id} when available.
