create_notification_rule
Create a notification rule that matches events by optional filters (project, source, event types, classes) and routes matching events to a Telegram chat binding.
Instructions
Create a Telegram routing rule: one match (project_id / source / event_types / classes, all ANDed, each optional — omitted = wildcard) routes to one Telegram binding. Requires operator_passkey assurance. An unusable or foreign telegram_binding_id returns the same 404 as a nonexistent one.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | No | Only match events from this source: 'app' (a deployed function's events.emit(...) calls) or 'platform' (deploys, lifecycle, verification, ...). Omit to match both. | |
| classes | No | Only match these notification classes (matches ANY listed value), e.g. 'lifecycle', 'app'. Omit to match any class. An empty array matches NOTHING (not a wildcard). | |
| project_id | No | Only match events for this project. Omit to match every project (wildcard). | |
| event_types | No | Only match these exact event_type names (matches ANY listed value). Omit to match any event_type. An empty array matches NOTHING (not a wildcard). | |
| telegram_binding_id | Yes | The Telegram binding (chat) this rule routes matching events to. Must be an active binding owned by this operator — see list_notification_channels. |