Pick a platform
If you’re not sure, start with Slack — it has the simplest setup. Pick Discord if you want chat-driven investigations with threaded follow-ups. Pick WhatsApp or Twilio SMS when your team already pages via Twilio.
You can configure more than one. Each is independent and uses its own credentials.
What every guide covers
Each platform guide walks you through:- Prerequisites — what you need before you start (workspace/server admin rights, a phone number for Telegram, a Twilio account for WhatsApp, etc.).
- Create the bot/app — the platform-side setup (BotFather, Discord Developer Portal, Slack App).
- Credentials — the exact tokens, IDs, and keys to copy.
- OpenSRE wizard — the
opensre onboardflow, what it asks for, and what it writes to.env. - Verify — how to confirm delivery is working.
- Troubleshooting — common failures and how to read the error.
Common environment variables
Discord and Telegram credentials can also be set directly in.env instead of (or alongside) the CLI configuration:
.env, run opensre integrations verify <service> (e.g. opensre integrations verify telegram, opensre integrations verify whatsapp, or opensre integrations verify twilio) to confirm the credentials work. Note that opensre doctor only inspects the integrations store (~/.opensre/integrations.json), so it does not detect env-var-only configurations like Telegram, WhatsApp, Twilio SMS, or Slack-via-SLACK_WEBHOOK_URL.
Re-running the wizard
You can re-run the Discord wizard at any time to update credentials:opensre integrations setup slack, opensre integrations setup whatsapp, and opensre integrations setup twilio. Telegram does not currently have a wizard step that persists credentials — use .env for Telegram (see #1481).