Start with email and webhook routes.
Integration · Product
FTStatus integrations
Connect FTStatus alerts to the tools your support and operations teams already use.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Add team chat and incident integrations only after test notifications pass.
Keep provider credentials redacted and scoped.
Watch the signal
Track the public evidence customers actually experience.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
Personal alerts
Email and SMS-style channels help individual owners respond quickly when configured.
Team alerts
Slack, Teams, Discord, Telegram, and webhooks help teams coordinate incident response.
Incident tooling
PagerDuty, Opsgenie, and similar routes should be enabled only after credentials and escalation rules are verified.
Validate
Test the destination before relying on it.
Attach
Choose the monitors or incidents that should notify.
Audit
Keep credentials redacted and errors observable.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.