Traffic Health External Notifications

Set up real-time Traffic Health alerts by email, Slack, or webhook — choose what triggers them, scope them to specific domains, and preview what recipients receive.

Introduction

Domain problems don't wait for business hours, and the people who most need to know (an on-call engineer, a client contact, a partnerships manager) don't always have an Everflow login. External Notifications close that gap. Say your track.brand.com lands on a blocklist at 2 a.m.: the right person hears about it in Slack before the first support ticket ever comes in. External Notifications let Traffic Health alert a key contact the moment a domain incident, task, or reputation flag is detected or resolved, through the channel that contact already lives in.

In v3, External Notifications support three channels: Email, Slack, and Webhook. Each notification is built around a single recipient, scoped to the domains you choose, and set up through the same three-step wizard. This article walks through creating, scoping, previewing, and managing them.

SMS is on the waySpotted SMS in the channel menu? It is coming soon. For now, Traffic Health reaches your recipients by Email, Slack, or Webhook, and SMS will join the lineup shortly.

Premium featureThe entire External Notifications screen is part of the Traffic Health Premium package. On Basic, you'll see an upgrade prompt instead of the management list, and the Reputation Flag alerts described below stay off. Everything in this article assumes Premium is active.

External Notifications vs. My Notifications Preferences

Everflow has two separate notification surfaces, and it's worth knowing which is which before you start.

External Notifications (this article) send alerts to a contact who may not have an Everflow account, over Email, Slack, or Webhook. Each one targets a single recipient and a chosen set of domains.

My Notifications Preferences control how you, the logged-in user, are notified in-app and by email, with a per-event cadence. These live under your account settings, apply only to your own login, and have no domain scoping.

If you want to alert someone without an Everflow seat, you're in the right place. If you want to change your own in-app or email cadence, head to My Notifications Preferences under your account instead.

Before You Start

Have these ready before you create a notification:

Premium plan: Traffic Health Premium is active on your network.

Recipient details: the contact's email address, or a Slack / Webhook URL for the destination app.

Domain list: which domains this contact should hear about, whether that's all of them or a specific set.

The External Notifications List

To reach the management screen, go to Traffic Health in the left navigation, then click Manage External Notifications in the top-right. This opens Manage External Notifications, where every notification you've created is listed. New notifications start from the External Notification button.

The Manage External Notifications list with channel rows and the + External Notification button

What Each Column Means

Scroll the table sideways to see every column. Each one tells you something about how a notification is configured:

Column

What it shows

Name

Your label for the notification: the recipient, channel name, or app you set on Step 1.

Type

The channel: Email, Slack, or Webhook.

Notification Status

Active (sending) or Inactive (saved but paused).

Destination

Where alerts go: the email address or webhook URL.

Notify of Incidents / Tasks / Flags

Which lifecycle hooks are on for each activity (for example, At Detection: Yes / At Resolution: No).

Domains

Either All or the specific domains this notification is scoped to.

Internal Note · Created · Modified

Your private note plus the audit timestamps.

You can narrow the list with the status pill (All / Active / Inactive) and the Table Filters flyout, which filters by Type and Domain.

The full External Notifications table scrolled to show every column

Editing, Pausing, and Deleting

Each row has a kebab (⋮) menu with three actions:

Edit: reopen the wizard to change the recipient, activities, or domain scope.

Set as Inactive: pause the notification without deleting it, then switch it back to Active any time.

Delete: remove it permanently. Deletion can't be undone, so a confirmation dialog asks you to confirm first.

The per-row actions menu showing Edit, Set as Inactive, and Delete

Bulk Actions

To pause or reactivate several notifications at once, select the rows you want. A selection toolbar appears showing how many are selected; open Actions → Update Status and choose Active or Inactive. A confirmation dialog applies the change to every selected row.

The selection toolbar with the Actions, Update Status submenu open

Setting Up an Email Notification

Click External Notification and choose Email from the Notify Via menu. The menu's three options (Email, Slack, and Webhook) are the only thing that differs at the start. From there, each channel runs the same three-step wizard: General → Domains → Preview.

Email

Names the recipient: Recipient Name

Sends to: an email address

Test action: none needed

Slack

Names the recipient: Channel Name

Sends to: a Slack Webhook URL

Test action: Test Webhook (sample message)

Webhook

Names the recipient: App Name

Sends to: a Webhook URL

Test action: Test Webhook (JSON payload)

STEP 1

General

STEP 2

Domains

STEP 3

Preview

On the email wizard's General step, fill in who receives the alerts. Fields marked with an asterisk (*) are required.

Recipient Name *: the person receiving the emails, for your own reference.

Email *: the address alerts are sent to.

Notification Status *: Active sends immediately, Inactive saves the setup without sending.

Internal Note: optional notes for your team, never sent to the recipient.

Then choose which events trigger an email under Notify of These Activities, covered in Choosing What Triggers a Notification below. Click Next to scope the notification to domains.

The Email notification wizard, Step 1 General, with Recipient Name and Email fields

Setting Up a Slack Notification

Choose Slack from the Notify Via menu. The General step is the same shape as Email, with one channel-specific field: instead of an email address you provide a Slack Webhook URL. This is the incoming-webhook URL you generate in Slack for the channel you want alerts posted to.

Channel Name *: your label for this notification (this is the same "Name" field other channels call Recipient Name or App Name).

Notification Status *: Active or Inactive, as above.

Slack Webhook URL *: the incoming-webhook URL from Slack.

Internal Note: optional, for your team only.

The Slack notification wizard, Step 1 General, with the Slack Webhook URL field and Test Webhook button

Before moving on, click Test Webhook. Traffic Health sends a sample message to the URL so you can confirm it lands in the right Slack channel. If nothing arrives within a few minutes, double-check the webhook URL.

The Test Webhook confirmation modal for Slack with a sample message preview

Setting Up a Webhook Notification

Choose Webhook to send alerts as a JSON payload to any endpoint that accepts incoming webhooks, whether that's a custom service, an internal tool, or an app like Discord. The General step mirrors the others, with a generic Webhook URL field.

App Name *: your label for this notification.

Notification Status *: Active or Inactive.

Webhook URL *: the endpoint that should receive the JSON payload.

Internal Note: optional, for your team only.

The Webhook notification wizard, Step 1 General, with the Webhook URL field

Click Test Webhook to send a small test payload to your endpoint. The test body identifies itself as a test so your receiving app can recognize it:

Test payload{ "traffic_health_notification": { "details": { "type": "test", "tester": "your name" } } }

The Test Webhook modal showing the JSON test payload

Webhook JSON Reference

Live alerts arrive as a traffic_health_notification object with two parts: a details block describing the event, and a support_notes block with your network name and point-of-contact text. An incident-detected payload looks like this:

Example: incident detected{ "traffic_health_notification": { "details": { "type": "Incident detected", "domain": "{Domain Name}", "detected": "{Detected}", "incident_id": "{Incident ID}", "incident_type": "{Incident Type}", "diagnosis_details": "{Diagnosis Details}" }, "support_notes": { "network_name": "{Network Name}", "contact_instruction": "For more details, communicate with your point-of-contact at {Network Name}." } } }

The keys inside details change with the activity type and lifecycle stage. Use this as a field reference when building your receiving logic:

Activity

Keys in details

Incident

type, domain, detected, incident_id, incident_type, diagnosis_details

Task

type, domain, detected, task_id (plus task_status and instructions on detection)

Reputation Flag

type, domain, detected, flag_type, flag_id, blacklist, blacklist_details

The support_notes block (your network name and contact instruction) is included on every payload regardless of activity type. The Preview step shows the exact JSON for each variant before you save, so confirm the shape there.

The Webhook Preview step showing the full JSON notification body

Choosing What Triggers a Notification

On the General step of any channel, the Notify of These Activities section is where you decide what actually fires an alert. There are three activity types, and each has two lifecycle hooks you turn on independently. So you can, for example, ping your on-call engineer the moment an incident is detected but stay quiet when it resolves.

Incidents

An issue that affects your uptime. Hooks: At Detection · At Resolution.

Tasks

Something you need to do to prevent or resolve an incident. Hooks: At Detection · At Completion.

Reputation Flags

A detected issue that may affect your traffic, like a blocklist hit. Hooks: At Detection · At Removal.

At least one hook must be on for an activity to send anything. The same three activities drive the Preview toggles on Step 3 and the Notify-of columns back on the list.

The Notify of These Activities section with Incidents, Tasks, and Reputation Flags toggles

Scoping Notifications to Domains

Step 2, Domains, decides which domains this notification covers. Under Domains Triggering the Notification, set the toggle to All or Specific.

Choose All to alert the recipient about activity on every domain in your network.

The Domains step with the All / Specific toggle set to All

Choose Specific to pick individual domains from the Available → Selected picker. Search across both lists, use Select All or Clear All, and move only the domains this contact should hear about. This is how you route one client's domains to their own contact without flooding them with everyone else's alerts.

The Specific domain picker with Available and Selected panes

The Preview Step

Step 3, Preview, shows exactly what the recipient will receive before you commit. Use the toggles (Incident / Task / Flag on one axis and the lifecycle stage on the other) to flip through every version your settings will produce. The preview renders in the channel's native format:

Email shows the full branded message: a subject line (for example, "Traffic Health - New Uptime Incident Detected"), a greeting, the event details, and a point-of-contact line.

Slack shows the message card as it posts to your channel, with a "Heads Up!" note that the live message may look slightly different.

Webhook shows the JSON payload for the selected event.

When the preview looks right, click Add to save the notification. If its status is Active, it starts sending on the next matching event.

The Email Preview step showing the rendered message and the type and stage toggles

The Slack preview works the same way, showing the message card instead of an email:

The Slack Preview step showing the message card and Heads Up banner

Pro-Tip:

Set up one notification per audience rather than one big catch-all. Send your on-call engineer Incidents → At Detection across All domains, and give each client contact a Specific, domain-scoped notification with just the hooks they care about. The single-recipient model makes this clean.

Frequently Asked Questions

Does the recipient need an Everflow account?

No. External Notifications are built specifically for key contacts who don't have an Everflow login. To change how you are notified instead, use My Notifications Preferences under your account settings.

Can one contact get alerts for only some domains?

Yes. Choose Specific on the Domains step and select just those domains from the picker.

Can I send the same alerts to several people?

Each notification targets a single recipient or destination. To alert several people, create one notification per recipient. They can share the same domains and activity settings.

How do I test a Slack or Webhook destination?

On the General step, click Test Webhook. Traffic Health sends a sample message (Slack) or test payload (Webhook) so you can confirm it arrives before saving.

How do I stop a notification?

Use the row's kebab menu to Set as Inactive (pause it) or Delete (remove it permanently). You can also bulk-update status from the selection toolbar.

What's Changed Last updated July 1, 2026 ▼

July 1, 2026 Added

External Notifications is new in v3, replacing the v2 "Manage Advanced Alerts" screen. It can alert people who don't have an Everflow account the moment a domain incident, task, or reputation flag fires.