Skip to content
Alertified Docs

Testing a channel

Every connected channelChannelA place Alertified sends notifications: Email, Telegram, Discord, Slack, Microsoft Teams, Webhook or ntfy. You connect channels in Settings and choose for each alert which ones it uses. Read more → except email has a Send Test Message button on its tab in Settings. A test messageTest messageA fixed message you send from a channel's tab in Settings with Send Test Message, to check that the channel is set up. It is not a stock alert. Read more → goes out straight away, through the same connection your alerts use, so you know the channel works before an alert needs it.

Send a test

Section titled “Send a test”
  1. Open Settings and the tab of a connected channel: Telegram, Discord, Slack, Teams, Webhook or ntfy.
  2. Click Send Test Message.
  3. Check the channel for the test message, and the tab for the result.

When the test reaches the channel, the tab shows a green banner:

| Tab | Banner | |---|---| | Telegram | Test message sent to Telegram! | | Discord | Test message sent to Discord! | | Slack | Test message sent to Slack! | | Teams | Test message sent to Microsoft Teams! | | Webhook | Test message sent to your webhook! | | ntfy | Test notification sent! |

The Emails tab has no test button. An alert email appears in Logs → Emails once an alert that uses Email notifies.

When a test fails

Section titled “When a test fails”

For Discord, Slack, Teams, Webhook and ntfy, a failed test shows a red banner built like this:

Discord test failed: the endpoint answered HTTP 404, nothing receives messages at this URL. It answered: "{"message": "Unknown Webhook", "code": 10015}". Check the URL in these settings, then send the test again.

It names the channel, the HTTP status the service answered, a short reason and what to do next. When the service answered with plain text, the banner quotes up to 120 characters of it after “It answered:”.

| Status | The banner says | What to check | |---|---|---| | 401, 403 | it refused access | Check that the URL still carries its token or key, then send the test again. | | 404, 410 | nothing receives messages at this URL | Check the URL in these settings, then send the test again. The webhook, workflow or endpoint may have been deleted. | | 405 | this URL does not accept messages | Check the URL in these settings, then send the test again. | | 408, 429 | it is busy or limiting requests | Wait a minute, then send the test again. | | 500 and above | it had an error of its own | Send the test again later; if it keeps failing, contact the service that runs this URL. | | Any other status | it refused the test message | Check the URL in these settings, then send the test again. |

To fix a wrong URL, click Disconnect, then connect the correct one.

Other messages you may see:

  • Telegram API error: followed by Telegram’s own description. Telegram could not deliver to the connected chat, for example because the bot was blocked in that chat. Disconnect and connect Telegram again.
  • Failed to send test message: followed by an error. Alertified could not reach the service at all. Check that the address is spelled correctly and that the server is online, then send the test again.

Where results appear

Section titled “Where results appear”
  • The test result appears only as the banner on the channel tab. Test messages are not listed in Logs.
  • Alerts are listed in Logs. Logs → Notifications shows every message to Telegram, Discord, Slack, Teams, Webhook and ntfy with Sent or Failed. Filter by channel and status; hover over Failed to see the error. Logs → Emails shows every alert email.

See also

Section titled “See also”

Contact support Impressum Datenschutz