Skip to content
Get Started Free
Public demo modeRead-only mock data for demo.errornotifier.com, shop.demo.errornotifier.com, api.demo.errornotifier.com, docs.demo.errornotifier.com, and hooks.demo.errornotifier.com. Placeholder secrets such as ensk_demo_placeholder_do_not_use are fake and cannot write data.
Create a real workspace

Simulated incident story

This demo data is read-only and follows one deploy from failing tests to recovery.

Simulated
  1. Bad deployStorefront release 2026.05-demo shipped with a checkout regression.
  2. Failed CI/test runGitHub Actions posted a failed unit test run with two checkout failures.
  3. Latency spikeAPI checks degraded while checkout health checks started returning errors.
  4. Confirmed incidentErrorNotifier opened a critical incident after repeated external failures.
  5. Alert routedEmail, Slack, and a signed automation webhook received delivery records.
  6. ResolutionThe deploy was rolled back, recovery was confirmed, and the report budget was updated.

Integration catalog

Foundation is implemented with database tables, REST routes, and docs. This page now shows the feed contract, current records, and the next setup action.

API docs

Integrations

Implemented channels are clearly separated from provider targets that need credentials and delivery enablement.

SlackImplemented
Incoming webhook notifications with structured incident and recovery payloads.
EmailImplemented
wp_mail delivery with branded incident subjects and digest-ready copy.
WebhooksImplemented
Signed outbound JSON with delivery logs and HMAC verification guidance.
PagerDutyProvider Target
Trigger, acknowledge, and resolve mapping for ErrorNotifier incident state.
Microsoft TeamsProvider Target
Incoming webhook or workflow-card mapping for incident and recovery notifications.
DiscordProvider Target
Channel webhook message mapping for community or operations rooms.
JiraProvider Target
Create-ticket and link-ticket workflow for confirmed incidents and grouped errors.
LinearProvider Target
Issue-linking workflow for engineering triage queues.
GitHubProvider Target
Release, commit, and issue association path tied to the release/artifact API.

Provider readiness

Provider targets define the event mapping, credential shape, and operator expectation before live delivery is enabled.

Active delivery

Use email, Slack, and signed webhooks for production alerts today. Add PagerDuty or Teams through the generic webhook path until native delivery is enabled.

Next docs

Open the integration guide for provider mapping and secret-handling rules.