Skip to main content
HealOps can deliver investigation findings — and accept investigation triggers — through three messaging platforms. Pick the one that matches where your team already responds to incidents.

​
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. You can configure more than one. Each is independent and uses its own credentials.

​
What every guide covers

Each platform guide walks you through:
  1. Prerequisites — what you need before you start (workspace/server admin rights, a phone number for Telegram, etc.).
  2. Create the bot/app — the platform-side setup (BotFather, Discord Developer Portal, Slack App).
  3. Credentials — the exact tokens, IDs, and keys to copy.
  4. HealOps wizard — the healops onboard flow, what it asks for, and what it writes to .env.
  5. Verify — how to confirm delivery is working.
  6. 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:
After editing .env, run healops integrations verify <service> (e.g. healops integrations verify telegram) to confirm the credentials work. Note that healops doctor only inspects the integrations store (~/.config/healops/integrations.json), so it does not detect env-var-only configurations like Telegram or Slack-via-SLACK_WEBHOOK_URL.

​
Re-running the wizard

You can re-run the Discord wizard at any time to update credentials:
Existing values are pre-populated, so you can press Enter to keep what you have. Slack and Telegram do not currently have wizard steps that persist credentials — use healops integrations setup slack for Slack and .env for Telegram (see #1481).