← Changelog/App

See which notifiers still need migrating

App·Oct 26, 2026

The External notifications page now marks deprecated notifiers with a Deprecated label. Its tooltip says what to set up instead. The label appears on:

  • Slack notifiers set up before the current Slack app. Select Migrate on the notifier's row to move it to the new Slack app.
  • PagerDuty notifiers. Set up a PagerDuty V2 API notifier instead.
  • MS Teams notifiers. Set up an MS Teams (Workflows) notifier instead.
The notifiers list with three legacy Slack notifiers marked Deprecated, each with a Migrate button next to Manage, below current Slack notifiers without the label

The deprecated PagerDuty and MS Teams notifiers can stop working at any time, so replace them soon. The Add new notifier list no longer offers them, so you can't set up a new one by mistake.

Read the Slack migration docs for what changes when you migrate a Slack notifier.

Notifier URLs must now be public. AppSignal only sends notifications to addresses on the public internet. It rejects webhook and other notifier URLs that point to localhost, a private network range, or another internal address. If an existing notifier points to one, AppSignal stops sending to it, and its log shows "Request blocked: URL does not resolve to a public address". Point the notifier at a public URL to start receiving notifications again.

$appsignal install

Make your next crash make sense.

Free for 30 days. No credit card. Two-minute install.