On this page

Slack

The Integrator posts alerts to Slack with the Web API method chat.postMessage, as a Slack app (bot). You need the app’s bot token (xoxb-…) and the channel to post to.

Step 1: create the Slack app

You need permission to install apps in the Slack workspace (or an admin who approves the request).

  1. Go to api.slack.com/apps and click Create New App → From scratch (shown as Blank app in the newer layout).
  2. Name it, for example Mugnsoft, choose your workspace, and click Create App.
  3. In the left menu, open OAuth & Permissions. Under Scopes → Bot Token Scopes, click Add an OAuth Scope and add:
    • chat:write — required, to post messages;
    • chat:write.public — optional, to post in public channels without inviting the app first.
  4. Scroll back to the top of OAuth & Permissions and click Install to Workspace, then Allow.
  5. Copy the Bot User OAuth Token. It starts with xoxb-.

Official guide: Slack — Quickstart with app settings. Scope reference: chat:write, chat:write.public.

Step 2: choose the channel and invite the app

  1. In Slack, open the channel, then its name → About (or Channel details). The Channel ID (C0123ABCD45) is at the bottom.
  2. Invite the app: type /invite @Mugnsoft in the channel.

Use the channel ID rather than the name: it survives a rename and is required for private channels. A private channel always needs the invitation, even with chat:write.public.

Step 3: configure Mugnsoft

Default for every monitor of an Integrator — Integrator → General → Notifications → Slack: switch On fail and/or On change on, then fill in Default channel (the channel ID) and Default token (the xoxb- token).

Per monitor — monitor → Actions → Slack card: switch the trigger(s) on. Leave Channel and Token empty to use the Integrator’s defaults, or fill in either one: a monitor can post to its own channel with the Integrator’s token.

Save both forms with the disk icon. See How an alert reaches someone for the switches involved.

What is posted

A message with a coloured side bar (status colour): the headline with a status emoji, the facts (type, status and duration, target, probe, check time), the probe’s message, a Locate in 3D view button and why the alert was sent. Phone and desktop notifications show the headline.

Test it

From Mugnsoft — in the Integrator’s Notifications block, click ⚡ on the Slack card. The Integrator posts a [TEST] Mugnsoft notification test message with the channel and token shown in the fields (or its saved defaults) and reports Slack’s error, if any (table below).

By hand — the same API call the Integrator makes, from the Integrator’s host:


curl -s -X POST https://slack.com/api/chat.postMessage \
  -H "Authorization: Bearer xoxb-your-token" \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{"channel":"C0123ABCD45","text":"Mugnsoft test message"}'

On Windows, run it in cmd or call curl.exe from PowerShell. Slack answers "ok":true and the message appears in the channel. Otherwise the error field says why (table below).

Then run the end-to-end test.

Troubleshooting

The Integrator logs the Slack error (sendMsgSlack - [monitor] - all 3 attempts failed: <error>).

Slack error Cause and action
not_in_channel The app is not a member of the channel: /invite @Mugnsoft, or add chat:write.public (public channels only) and reinstall.
channel_not_found Wrong channel ID or name, or a private channel the app was not invited to.
invalid_auth / not_authed Wrong or revoked token, or a webhook URL instead of a bot token.
token_revoked / account_inactive The app was uninstalled or its installer left the workspace: reinstall it and update the token.
missing_scope chat:write is missing: add it and reinstall the app (scopes apply only after reinstalling).
ratelimited Too many messages: an ON FAIL rule for 0 checks on many monitors posts at every check. Use for N checks or ON CHANGE.

Error reference: chat.postMessage. More in Troubleshooting.

Translations

Microsoft Teams