Notifications are how TigerTrust reaches the humans and systems that need to act. Every alert, approval request, workflow event, or ad-hoc message flows through a channel (where it goes), optionally through a template (what it says), and optionally through an escalation rule (who gets paged next if nobody responds).
Notifications

​
What it is

You configure one or more notification channels — Slack, email, PagerDuty, Teams, a signed webhook, or SMS — and then reference those channels in alert rules, workflow steps, and escalation policies. Every channel can be tested with a synthetic delivery before it is used in production.

​
When to use it

  • Send expiry alerts to a Slack channel watched by the infrastructure team.
  • Page the security on-call via PagerDuty for critical alerts, while routing low-severity alerts to email.
  • Route approval requests to a specific Teams channel so approvers see them immediately.
  • Stream every alert event to a SIEM via a signed webhook.

​
Channel types

TypeWhat you configure
emailSMTP or transactional email service, recipient list
slackIncoming webhook URL, optional channel override
teamsMicrosoft Teams incoming webhook URL
pagerdutyEvents API v2 routing key
opsgenieAPI key and region
webhookTarget URL, optional headers, HMAC secret for signature verification
smsTwilio account credentials, recipient phone number

​
Set it up

1

Open notification settings

Go to Settings > Notifications and click Add channel.
2

Choose a channel type

Select the type and enter the required configuration. For Slack, paste the incoming webhook URL. For PagerDuty, paste the Events API v2 routing key.
3

Test the channel

Click Send test. TigerTrust sends a real message through the channel using the same delivery path as production alerts. A successful test confirms the channel is ready.
4

Create a message template (optional)

Click Templates > New template to customize the message body for a specific event type. Use Handlebars-style variables such as {{certificate.commonName}}, {{daysUntilExpiry}}, and {{severity}}. If no template matches, TigerTrust uses a built-in default.
5

Configure escalation rules (optional)

Click Escalation rules > New rule to define a tiered response. Set conditions (severity, resource type) and escalation levels with per-level channels and delay times. If the first-tier channel does not acknowledge within the configured delay, the next tier fires.

​
What you’ll see

Settings > Notifications shows all channels with a status indicator — a red dot on any channel whose last delivery attempt failed so you can fix it before a real incident. Each channel shows lastTestedAt and successRate. Escalation rules list active rules with trigger conditions and tier configuration. You can enable or disable a rule without deleting it.
Webhook targets receive an HMAC-SHA256 signature in the X-TigerTrust-Signature header when you set an HMAC secret. Always verify the signature on your end — an unauthenticated webhook endpoint is a security risk.
The API surface for notification channel management is documented at API Reference.

Alerts

The rules that produce the notifications.

Workflows

Send notifications from any workflow step.