Available integration
Connect an HTTP-capable sender through one release-gated contract
MonoDuty currently publishes one generally available integration surface: the universal HTTP Webhook. Named adapters remain out of the live catalogue until they pass their own end-to-end release gates.
No credit card required · paid activation is sales-assisted
01 / Directory
Available now
Only release-gated integrations appear in this directory. Named adapters move here after backend, UI, and delivery tests pass.
02 / Overview
Start with the production payload contract
The release-gated MonoDuty directory currently lists Universal HTTP Webhook. A sender must POST the documented JSON shape to its service-specific mndty.com URL.
The Webhook accepts a title or message plus optional severity, description, source, metadata, and deduplication key. Email, SMS, and voice are the currently release-gated delivery channels.
03 / Operating value
Keep each sender accountable
A useful connection has an owner, a documented payload, and a repeatable test.
Preserve source responsibility
The source keeps its detection role while MonoDuty handles incident ownership and response routing.
Use a stable schema
Require a title or message and send source context in the documented source and metadata fields.
Test retry behavior
Use an Idempotency-Key and verify both same-payload replay and conflict behavior before production.
04 / Workflow
Connect a source without inventing an adapter
Transform the sender payload into the documented native shape, then validate the complete response path.
- 01
Create an owned service source
Create the source under the correct team-owned service and copy its one-time Webhook URL securely.
- 02
Map the payload
Send title or message; map optional context into description, source, metadata, severity, and dedup_key.
- 03
Run a controlled alert
Confirm the first request, idempotent retry, conflicting retry, on-call ownership, and notification delivery.
05 / Plans
Choose the response capacity around the integration
Plan selection should reflect incident volume, team size, channels, and retention—not just the integration name.
Free
One user, 50 incidents/month, email, and 7-day retention.
Pro
Up to 25 users, 5,000 incidents/month, email/SMS/voice, escalation policies, and 30-day retention.
Business
Unlimited users and incidents, email/SMS/voice, escalation policies, and 90-day retention.
06 / Questions
Common questions
01Which integration is generally available?
The release-gated directory currently lists Universal HTTP Webhook.
02Are native Slack, Discord, or Microsoft Teams channels live?
No. They remain unreleased and are not part of the current production contract.
03Can any tool post its native payload unchanged?
No. The sender must produce the documented MonoDuty Webhook fields; named native adapters are not implied.
MonoDuty / Start
Connect one sender and test the complete route
Start with a representative payload mapping and verify validation, deduplication, ownership, delivery, and fallback before expanding.