Skip to content

Integrations

Email, Slack, and signed webhooks are the implemented alert channels today. PagerDuty, Microsoft Teams, Discord, Jira, Linear, and GitHub are documented provider targets so teams can review the intended event mapping before credentials and delivery are enabled.

ProviderStatusEvent mappingSetup note
EmailImplementedIncident opened, recovery, and digest messages.Back wp_mail with SPF, DKIM, and DMARC.
SlackImplementedStructured incident and recovery notifications through incoming webhooks.Store webhook URLs as protected secrets.
Signed webhooksImplementedHMAC-signed incident events for custom receivers and automation.Verify X-ErrorNotifier-Signature before creating downstream tickets.
PagerDutyProvider TargetTrigger, acknowledge, and resolve incidents from ErrorNotifier incident state.Requires service integration key and escalation policy review before delivery is enabled.
Microsoft TeamsProvider TargetPost incident cards to Teams channels through incoming webhook or workflow URL.Requires tenant-approved webhook/workflow endpoint.
DiscordProvider TargetPost incident notifications to operations or community channels.Requires channel webhook secret and formatting review.
Jira and LinearProvider TargetCreate or link issue records from confirmed incidents and grouped errors.Requires project/team mapping and duplicate handling.
GitHubProvider TargetAssociate commits, releases, and issues with incident or error context.Use release/artifact API first for build context.

Security rule

Do not paste provider secrets into issue comments, logs, public pages, release metadata, or webhook payload examples. Use protected alert-channel storage and rotate credentials when a provider URL or token is exposed.

Public demo

Review the real product screens with read-only mock data

Open the demo workspace to inspect monitors, incidents, domains, alert channels, status pages, projects, issues, automated test runs, releases, artifacts, audit history, and umbrella reports without creating an account.