Delivery Channels
When an alert rule fires, Opsion dispatches notifications over every channel you have enabled for that rule. You can combine channels freely — for example, send critical alerts to both Slack and email, while low-severity rules go to email only.
Overview
| Channel | Setup location | Per-rule override |
|---|---|---|
| Settings → Organisation (notification email) | No — org email used for all rules | |
| Slack | Settings → Notifications (Slack Webhook URL) | No — org webhook used for all rules |
| Lark | Settings → Notifications (Lark Webhook URL) | No — org webhook used for all rules |
| Telegram | Settings → Notifications (Telegram Chat ID) | Yes — rule can override with a different chat ID |
| Custom webhook | Alert rule configuration | Yes — set per rule |
Org-level vs per-rule configuration
Most channels (Slack, Lark, email) are configured once at the organisation level in Settings → Notifications. Any rule that has that channel enabled uses the org-level endpoint automatically — you do not need to re-enter credentials for each rule.
Telegram supports an additional per-rule Chat ID override. This lets you route different alert rules to different Telegram groups or individuals without changing the org-level default. Custom webhooks are always per-rule, since each integration typically points at a different endpoint.
Enable channels on a rule
Each alert rule has a Notification channels section. Toggle the channels you want for that rule. A channel must also be configured at the org level (or per-rule for Telegram and webhooks) for notifications to be dispatched.Opsion sends alert emails from alerts@opsion.xyz using a structured template that includes the rule name, severity, transaction details, and a direct link to view the transaction on a block explorer.
The recipient address is taken from Settings → Organisation → Notification email. If no notification email is set, alerts fall back to the organisation owner's account email.
See the Email setup guide for full details.
Slack
Slack notifications use an incoming webhook URL that you create inside Slack. Messages are sent as plain text with bold formatting and include a clickable link to the block explorer.
See the Slack setup guide for step-by-step instructions.
Lark
Lark notifications use a custom bot webhook URL. Add the bot to any Lark group or direct message thread, copy its webhook URL, and paste it into Settings.
See the Lark setup guide for step-by-step instructions.
Telegram
Telegram notifications are sent via the Opsion Telegram bot. You provide your Chat ID (for a personal chat or a group) and the bot will send formatted messages with a transaction link.
See the Telegram setup guide for step-by-step instructions.
Custom webhook
Custom webhooks fire an HTTP POST request to any public HTTPS URL you specify. The payload includes the rule details, transaction metadata, and a block explorer URL. See the Webhooks reference for the full payload schema and signature verification.