Integration

Send urgent certificate warnings to the Slack channel your team watches.

Use Slack incoming webhooks for final-week expiry warnings, validation failures, and public certificate changes that need fast human attention.

Alert routingAlerting docs

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
Route by workspace, hostname, channel, and severity
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.

01

Connect the right channel

Connect Slack from the notification channel page, choose the channel that handles renewal, CDN, platform, or client-domain issues, then send a test alert before routing critical events.

  • Use a channel watched by the team that can renew, deploy, or escalate.
  • Avoid personal channels for shared certificate responsibility.
  • Use alert route filters to send final-week, expired, validation, or change events to Slack.
  • Use reconnect after Slack workspace, channel, or app permission changes.
Slack setup flow
StepActionSuccess state
1Create or choose a channel watched by the renewal or platform owner.The channel name makes the alert purpose obvious.
2Start the Slack connection from Domain Trust Watch.Slack opens its OAuth channel picker.
3Approve the selected channel.The Slack channel appears in alert routing settings.
4Send a test delivery before attaching critical events.The test message arrives and the delivery attempt is visible.
02

Know what the message should tell you

A useful Slack warning should make the hostname, urgency, deadline, and next action visible without forcing the team to rerun a manual check first.

  • Example: api.example.com has 7 days left.
  • Example: checkout.example.com failed hostname validation.
  • Example: docs.example.com is serving a certificate with a changed issuer.
Slack message anatomy
FieldExampleWhy it helps
Hostnameapi.example.comShows the endpoint to inspect or renew.
SeverityCritical validation failureSeparates urgent action from routine review.
Deadline7 days leftShows how much runway remains.
Event typeExpiry warning or hostname mismatchRoutes the fix to renewal, platform, DNS, or CDN owner.
Next actionRenew and verify served certificateReduces the need to rerun checks before triage.
Monitor linkOpen monitor detailKeeps certificate snapshot and delivery history one click away.
03

Test before relying on it

Use the dashboard test action after creating or rotating a webhook. Delivery attempts show whether the test succeeded or failed before urgent warnings depend on the channel.

  • Run a test after webhook creation.
  • Retest after channel permission or webhook URL changes.
  • Fix failed test deliveries before routing final-week expiry warnings.
  • Use event and expiry-window filters before relying on Slack for urgent-only alerts.
FAQ1 answer

  1. How does the Slack integration connect?

    The Slack integration uses Slack OAuth to create an incoming webhook for the selected channel. Manual incoming webhook URLs are still supported as a fallback, but OAuth is the primary dashboard flow.

Related3 pagesSSL expiry monitoringSee staged warning thresholds before expiry.Explore SSL expiry monitoring
PricingPricingChoose the monitored hostname count and alert channels your team needs.PageSecurityReview public probing and private-key boundaries.
Test the channel

Run one hostname check before sending warnings to Slack.

Use the checker for the current certificate, then connect Slack when the hostname needs recurring warnings.

Run SSL checkerRead alerting docs