Integrations

Wired into the surfaces your team already uses.

Slack, Discord, signed webhooks, and email — plus a clean REST API and event stream for everything you’d rather build yourself. No middleware, no glue code, no third-party iPaaS in the path.

Start free trial

API reference

Slack

Routes incidents into the Slack channel that owns the affected service. Threaded follow-ups, severity badges, and one-click resolution actions sit inline with the brief.

Key features

Per-channel ownership routing
Threaded follow-ups on the same incident
Inline resolve and acknowledge
Severity-aware formatting

Setup

Authorize via OAuth in Settings → Integrations → Slack, pick a default channel for the workspace, and add ownership rules to send specific incidents elsewhere.

Discord

Webhook-delivered incident embeds with severity colour coding. Built for community-run infrastructure and ops channels that already live on Discord.

Key features

Webhook-based, no bot install required
Embedded incident briefs
Colour-coded severity
Channel-scoped routing

Setup

Generate a channel webhook inside Discord, paste the URL into Settings → Integrations → Discord, and bind it to the alert rules that should fire there.

HTTP webhooks

Signed JSON payloads delivered for every incident lifecycle event. Drop in front of PagerDuty, Opsgenie, or whatever already sits in front of your on-call rotation.

Key features

Configurable method, headers, and TLS
Full incident JSON, including the diagnosis brief
Exponential-backoff retries with at-least-once delivery
HMAC-SHA256 signed payloads

Setup

Register the endpoint in Settings → Integrations → Webhooks, choose the event types to subscribe to, and verify with the built-in test delivery.

Email

Delivered as plain-text and HTML, with the full incident brief in the body. No third-party redirects, no tracking pixels, no marketing footers.

Key features

HTML and plain-text bodies
Per-user delivery preferences
Optional daily digest mode
One-click unsubscribe per channel

Setup

Email is enabled by default for the workspace owner. Add additional recipients in Settings → Members and configure per-recipient quiet hours.

API surface

A clean REST API for the rest.

Hosts, incidents, metrics, alert rules, and audit history — accessible programmatically with scoped tokens. Designed to be readable from a terminal, not a TypeScript SDK.

REST API

Programmatic access to hosts, incidents, metrics, and alert rules. Standard HTTP verbs, JSON payloads, predictable resource layout.

Scoped tokens

Workspace tokens issued from the dashboard, with per-resource scopes and individual revocation. No long-lived service accounts.

Streaming events

Subscribe to host state and incident lifecycle events over a long-lived connection for real-time downstream pipelines.

Outbound webhooks

Signed deliveries for every incident state change — created, escalated, diagnosed, resolved — with at-least-once semantics.

Sample webhook delivery

curl -X POST https://api.pulsewise.io/v1/webhooks/test \
  -H "Authorization: Bearer pw_live_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "incident.created",
    "host": "db-prod-01",
    "severity": "critical",
    "brief": "Postgres reaped by OOM killer; long-running query + pool spike"
  }'

Full API reference

On the roadmap

Native integrations currently in build.

Customer-driven priorities. If something here unblocks your team, say so — it moves up the queue.

PagerDuty (native)
Opsgenie (native)
Microsoft Teams
Telegram
Datadog (export)
Grafana (data source)
Jira
Linear

Request a specific integration

Wired into the surfaces your team already uses.

Slack

Discord

HTTP webhooks

Email

A clean REST API for the rest.

REST API

Scoped tokens

Streaming events

Outbound webhooks

Native integrations currently in build.

Get started in under a minute.