Skip to main content
FeaturesIntegrations
Integrations

Connect once. Encrypt at rest. Inspect every delivery.

Every integration credential is AES-256-GCM encrypted. Every outbound webhook is HMAC-signed. Every delivery is captured in the inspector for forensic debugging.

9
Integration types
AES-256-GCM
Credential encryption
HMAC-SHA256
Webhook signing
Per-attempt
Delivery inspector

Chat & collaboration

Slack, Microsoft Teams and Discord — interactive actions on Slack, adaptive cards on Teams, rich embeds on Discord.

  • Slack — bot token or webhook URL connection modes
  • Microsoft Teams — adaptive card payloads
  • Discord — severity-coloured rich embeds
  • Per-channel routing rules
  • Token rotation without re-deploying

Paging tools

PagerDuty and Opsgenie with bi-directional close — resolve in the paging tool, the incident closes here too.

  • PagerDuty Events API v2
  • Opsgenie native dedup keys
  • Bi-directional resolution
  • Per-service routing-key override

Email & SMS

SMTP for branded transactional email; Twilio for SMS with reply-to-ack where carriers allow.

  • SMTP relay — per-org sender domain
  • SPF / DKIM aligned delivery
  • Twilio SMS with reply-to-ack
  • Per-recipient opt-out preference
  • Per-org SMTP sender identity (white-label email)Roadmap

Generic webhooks

HMAC-SHA256 signed, retried with exponential backoff. Every attempt visible in the inspector.

  • HMAC-SHA256 signature on every request
  • Configurable retry policy with exponential backoff
  • Per-webhook delivery inspector
  • Replay-attack protection via timestamp tolerance
  • Per-webhook custom headers
http
POST /hooks/alertify HTTP/1.1
X-AlertifyPro-Signature: sha256=a3f1...
X-AlertifyPro-Timestamp: 1750497600

{ "event": "alert.fired", "...": "..." }

Mobile push (FCM + APNs)

Push delivery to your registered iOS and Android devices — first-class integration, not a third-party relay.

  • FCM for Android, APNs for iOS
  • High-priority delivery
  • Critical-alert override on iOS (Pro+)
  • Per-device quiet hours

Credential security

Every integration credential AES-256-GCM encrypted with per-org data keys. Decryption only happens in the notification worker at delivery time.

  • AES-256-GCM with per-org data-encryption keys
  • Master key wrapping for the per-org keys
  • Decryption only in the notification worker process
  • Per-credential audit trail (created, rotated, used)
  • One-click revocation

Delivery inspector & health

Every attempt captured with full request/response. Per-integration failure rate graphs. Retry-now from the dashboard.

  • Per-attempt request and response capture
  • Per-integration failure rate graph
  • Retry-now button with the same payload
  • Per-channel health badge on the integration list

REST + WebSocket API

Everything the dashboard does, scriptable. Per-key scopes, rate limits and audit. Terraform on the roadmap.

  • REST API at /api/v1/*
  • WebSocket push for live updates
  • Per-key scopes (read or write)
  • Per-key rate-limit overrides
  • Terraform provider for configuration-as-codeRoadmap
  • GraphQL API (alongside REST)Roadmap
Integrations vs the market

How we stack up on integrations

Only rows relevant to this capability. See the full comparison →

FeatureAlertifyProDatadogUptimeRobotPingdom
9 integration types out of the box
AES-256-GCM credential encryption
HMAC-SHA256 webhook signing
Per-attempt delivery inspector
Bi-directional PagerDuty / Opsgenie close
Terraform providerRoadmap

Frequently asked

Ready to see integrations on your stack?

Spin up your first monitor in under a minute. Free forever for the first 5 services.