Alert channels
Pre-built notification templates that turn Discord, Slack, Telegram, and other services into MCP tools.
How alert channels work
Each alert channel is a pre-configured MCP tool. You provide credentials or a webhook URL once in the dashboard; Herald stores them encrypted and handles the HTTP request format when your agent invokes the tool.
- Go to Alerts → Add alert channel in your workspace
- Choose a template (Discord, Slack, Telegram, …)
- Enter the webhook URL or config fields (bot token, chat ID, etc.)
- Send a test alert from the setup wizard
- The tool appears in MCP once your IDE is connected
Available templates
Team chat
- Discord — incoming webhook URL
- Slack — incoming webhook URL
- Microsoft Teams — connector webhook URL
- Google Chat — space webhook URL
- Mattermost — incoming webhook
- Rocket.Chat — incoming webhook
Mobile & push
- Telegram — bot token + chat ID
- ntfy — topic URL
- Gotify — server URL + app token
- Pushover — user key + application token
Incident & automation
- PagerDuty — Events API v2 integration key
- Zapier / Make / IFTTT — catch hook URLs
Structured alerts
- Security Alert Pack — Discord embeds and Telegram markdown for severity, details, dedup keys
- Web3 Alert Pack — on-chain alerts with tx hash, chain, and explorer links
How you configure them
Most chat tools need a single webhook URL from Discord, Slack, Teams, and similar. Telegram, PagerDuty, and a few others ask for named credentials (bot token, chat ID, integration key). Custom HTTP tools are configured under Custom tools.
No webhook URL?
If you don't have a Discord/Slack webhook yet, create a Herald webhook first and point a custom tool or automation at it. Events appear in your Inbox and can be read by MCP inbox tools.
Managing channels
- View all channels on the workspace Alerts page
- Enable or disable individual tools without deleting them
- Update credentials from the tool’s configure screen when a webhook rotates