Works with your existing tools
Keep your monitoring stack. Connect your alert sources to Acked, then notify and escalate to the right people.
Choose a source, copy its endpoint and credential, and send a test alert. Each setup guide explains the required sender configuration.
Standard integrations, push, and email are included on every plan. Voice is available on Team and Business and billed separately.
Monitoring and alert sources
Connect a native adapter, send a compatible API payload, or map your own JSON.
-
Grafana Alerting
Inbound · Native adapter
Receive Grafana alerts and recoveries using its default webhook body.
- Capabilities
- Grouped alerts, deduplication, recovery, and routing by alert labels.
- Setup and requirements
- Create a webhook contact point with the Acked ingest URL.
-
Prometheus Alertmanager
Inbound · Native adapter
Receive standard Alertmanager webhooks and route each alert to its service.
- Capabilities
- Grouped alerts, deduplication, recovery, and routing by alert labels.
- Setup and requirements
- Set the webhook URL and enable send_resolved for recoveries.
-
Datadog
Inbound · Webhook adapter
Receive Datadog monitor alerts and recoveries through a webhook.
- Capabilities
- Priority mapping, deduplication, recovery, and routing from Datadog tags.
- Setup and requirements
- Paste the payload supplied by Acked into Datadog’s webhook configuration.
-
AWS CloudWatch
Inbound · Signed SNS messages
Receive CloudWatch alarm alerts and recoveries through Amazon SNS.
- Capabilities
- Signature verification, deduplication, recovery, and routing by alarm attributes.
- Setup and requirements
- Create a standard SNS topic and HTTPS subscription. Send both Alarm and OK actions to the topic.
-
Azure Monitor
Inbound · Common Alert Schema
Receive Azure Monitor alerts and recoveries through an action group webhook.
- Capabilities
- Severity mapping, deduplication, recovery, and routing by alert attributes.
- Setup and requirements
- Add a Webhook action and enable the common alert schema.
-
Google Cloud Monitoring
Inbound · Webhook notifications
Receive Google Cloud Monitoring incidents through a webhook notification channel.
- Capabilities
- Severity mapping, deduplication, recovery, and routing by incident attributes.
- Setup and requirements
- Attach a webhook channel to your alerting policy. Enable closed-incident notifications for metric policies.
-
PagerDuty Events API v2
Inbound · Compatible API format
Receive compatible Events API v2 payloads using an Acked endpoint and routing key.
- Capabilities
- Trigger, acknowledge, resolve, and case-sensitive deduplication keys.
- Setup and requirements
- The sender must support a custom destination. Payload compatibility does not migrate PagerDuty configuration or history.
-
Acked HTTP Monitors
Inbound · Built-in HTTP checks
Check public HTTP and HTTPS endpoints every minute and page on failures.
- Capabilities
- Configurable success codes, failure and recovery thresholds, and incidents routed to the selected service.
- Setup and requirements
- Creation is rolling out to selected organizations. An admin creates each monitor within the plan limit. Contact hello@acked.dev for access.
-
HTTP API and webhooks
Inbound · Acked JSON
Send alerts from scripts or any tool that can post Acked JSON over HTTP.
- Capabilities
- Trigger, deduplication, and recovery through the alert API or a service ingest URL.
- Setup and requirements
- Use an API key or the service’s secret ingest URL.
-
Custom JSON mapping
Inbound · Custom mapping
Map an existing sender’s JSON payload to Acked alert fields.
- Capabilities
- Map title, event key, priority, urgency, action, and routing attributes.
- Setup and requirements
- Configure and preview a mapping with a representative payload.
-
Email alerts
Inbound · Email source
Turn messages sent to a service’s dedicated email address into alerts.
- Capabilities
- The subject becomes the title and the message becomes the details.
- Setup and requirements
- Each message creates a separate alert with high priority and urgency.
Notifications
Page the on-call responder and send lifecycle events to your own systems.
-
iOS and Android push
Outbound · Mobile notifications
Notify on-call responders on their iOS and Android devices.
- Capabilities
- Push notifications with alert response actions in the mobile apps.
- Setup and requirements
- Every plan. Install the app and enable notifications; verify device readiness.
-
Email
Outbound · Email notifications
Page responders by email with a link to acknowledge the alert.
- Capabilities
- Alert details and signed acknowledgement links.
- Setup and requirements
- Every plan. Delivery follows the responder’s configured channel policy.
-
Voice
Outbound · Voice paging
Call on-call responders when your paging policy includes voice.
- Capabilities
- Voice calls to verified personal or work numbers.
- Setup and requirements
- Team and Business. Billed separately. An admin must enable voice and each responder must verify a number.
-
Outbound webhooks
Outbound · HTTPS delivery
Send alert lifecycle events to your own HTTPS receivers.
- Capabilities
- Event and service selection, signed requests, retries, and custom payload templates.
- Setup and requirements
- Every plan. Custom formats require a template; receivers must verify signatures and handle retries.
Chat and collaboration
Keep alert updates in the channels your team already uses.
-
Slack
Bidirectional · Slack app
Post alert updates to channels and acknowledge, escalate, or resolve from Slack.
- Capabilities
- Channel destinations, lifecycle updates, and linked-user response actions.
- Setup and requirements
- Every plan. An admin connects the workspace; response actions require a linked Acked user with access.
-
Discord webhook
Outbound · Webhook format
Send alert lifecycle messages to a Discord channel through an incoming webhook.
- Capabilities
- Provider-ready messages for selected lifecycle events.
- Setup and requirements
- Every plan. Choose the Discord webhook format. Response actions are available in Acked.