Destinations for OpenClaw Alerts
Once OpenClaw policies are triggering, route them to destinations so the right people or systems see them.
Common choices:
- Slack for team-facing alert triage
- Discord for community or ops rooms
- email for low-volume workflows
- webhook destination for custom incident or automation pipelines
- Telegram for lightweight mobile delivery
Current baseline support is:
- supported:
webhook,email,slack,discord,telegram - not part of the v1 supported destination baseline:
sms
Validation rules
- Slack requires a valid Slack destination URL
- Discord requires a valid Discord destination URL and a path containing
/webhooks/ - Telegram requires
credentials.bot_tokenandcredentials.chat_id - Email destinations use the
urlfield as the destination email address - Generic webhook destinations require an absolute
url
Recommended testing flow:
- create the destination
- send a test notification and capture the returned
alert_id - inspect
GET /v1.0/alerts/:alertID/deliveries?kind=testusing thatalert_id - trigger a real alert and inspect the default delivery history view
Test deliveries are hidden from the default delivery history view, so use kind=test immediately after destination setup.
Exact test lookup example
Raw API
TEST_ALERT_ID=$(curl -s -X POST \
-H "Authorization: Bearer $CHIRPIER_API_KEY" \
https://api.chirpier.co/v1.0/destinations/$DESTINATION_ID/test | jq -r '.alert_id')
curl -G https://api.chirpier.co/v1.0/alerts/$TEST_ALERT_ID/deliveries \
-H "Authorization: Bearer $CHIRPIER_API_KEY" \
--data-urlencode "kind=test"Delivery history supports:
kind=alertkind=testkind=all
Last updated on