Integrations

Route certificate warnings to the channel that can act.

Use email for early renewal reminders, Slack for watched operational channels, and signed webhooks when expiry, validation, or certificate-change events should update internal systems.

Alert route

Critical warnings are routed

Slack + email

Expiry, validation, and certificate-change events keep the route and delivery attempts attached to the hostname.

SeverityFinal-week expiry
Slack#certificates delivered
WebhookSigned payload ready
01

Email alerts

Use email for 30-day and 14-day expiry reminders, renewal planning, account-team visibility, and a searchable record of early certificate warnings.

Explore email certificate alerts
02

Slack warnings

Use Slack for watched operational channels that should see 7-day, 3-day, 1-day, expired, validation-failure, or review-worthy certificate-change events.

Explore Slack certificate alerts
03

Signed webhooks

Use signed webhooks when certificate events should create tickets, update inventory, feed client reporting, or enter incident routing after the receiver verifies the signature.

Explore signed webhook alerts
Alert routing

Route warnings by workspace, hostname, channel, and severity.

Alert routes show which events go to Slack, email, or signed webhooks before a missed warning becomes a second problem.

Routing decisions

Connect channels after deciding who owns the next action.

A certificate warning should include enough context to assign renewal, DNS, CDN, load balancer, or receiver cleanup work without rerunning every probe first.

Integration library

All alert integration pages.