Connect sources

Receive signals from monitoring tools, email, or custom JSON.

Create a source

Open Integrations → Sources to review every source in the organization. Source credentials and actions stay with their service.

1. Open Services and select the service.
2. Find Sources.
3. Select Add source.
4. Name the sender and choose its type.
5. Create the source.
6. Copy the ingest URL, email address, or routing key from the one-time prompt.

Keep the credential secret. Anyone who holds it can create alerts for the service.

Webhook source

Use Webhook when the sender can send Acked JSON. Send the request to the ingest URL shown after source creation.

curl -X POST "<YOUR-INGEST-URL>" \
  -H "content-type: application/json" \
  -d '{
    "event_key": "checkout-latency",
    "title": "Checkout latency above 2 seconds",
    "priority": "high"
  }'

Send "action":"resolve" with the same event key when the condition clears.

Datadog

1. Create a Datadog source on the service.
2. Copy the ingest URL and payload shown by Acked.
3. In Datadog, open Integrations → Webhooks → New.
4. Use the ingest URL as the webhook URL.
5. Paste the Acked payload into Datadog’s Payload field.
6. Add the webhook to the monitor notification list.

The payload maps Datadog alert and recovery transitions to the Acked alert lifecycle.

Prometheus Alertmanager

Create an Alertmanager source. It accepts the standard Alertmanager webhook format, including batches.

receivers:
  - name: acked
    webhook_configs:
      - url: <YOUR-INGEST-URL>
        send_resolved: true

Acked creates one alert for each firing item. It uses the Alertmanager fingerprint for deduplication and resolves recovered items.

Grafana Alerting

1. Create a Grafana Alerting source.
2. Create a Grafana contact point that uses the Acked ingest URL.
3. Keep Grafana’s default webhook body.
4. Send a test notification from Grafana.

Acked creates one alert for each item in alerts[]. It uses the item fingerprint for deduplication and recovery.

PagerDuty Events API v2

This source is a compatibility layer. It accepts existing PagerDuty Events API v2 payloads.

1. Create a PagerDuty Events API v2 source.
2. Change the sender endpoint to https://api.acked.dev/v2/enqueue.
3. Replace the routing key with the key shown by Acked.
4. Keep the existing event payload.

Acked accepts trigger, acknowledge, and resolve actions. It preserves the case-sensitive dedup_key.

Email

Create an Email source and copy its address. Each message opens a separate alert. The subject becomes the alert title, and the message becomes the details.

Email alerts use high priority and high urgency. Message content cannot override those values.

Custom payload mapping

Use Custom when a vendor sends a fixed JSON shape that Acked does not support directly.

1. Paste a representative payload into the tester.
2. Map its values to title, event key, priority, urgency, and action.
3. Preview the resulting alert.
4. Save the source and send a vendor test.

Rotate or revoke a source

Select Reveal to show the current credential in the source box. Select Rotate when the credential is exposed or must change.

Rotation replaces the credential. Revocation disables the source. The previous credential stops working within one minute.