Alert delivery

What this feature is for

Alert delivery routes monitor failures, payment drift, release blockers, and incidents to Slack, email, Discord, or a webhook. It is a delivery system, not a generic notification feed. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A configured channel, a recipient who owns the response, and severity rules that reflect business impact.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Create the channel, test delivery, choose event types and severity, then review delivery history after the first real event.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

Each delivery records channel, event, timestamp, attempt status, and a safe error when delivery fails. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

A valid token does not prove channel access. Test the exact target, invite the bot where required, and rotate a credential only after confirming the replacement.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use Alerts with Incidents, Revenue Watch, Release desk, and Uptime monitors. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.