Ackline

Integrations

Ackline works with the tools you already run. This page says plainly what exists today, what is being built and what is only planned.

Available means built and deployed in the Ackline backend. In progress means work has started. Planned means on the list and not started. Ackline itself is not yet released, so nothing here is available to customers yet. The order below is the build order, and it can change with what teams tell us they use.

1. Alert sources

Monitoring tools that send alerts into Ackline by webhook, authenticated with a secret.

ToolStatusWhat it means
Prometheus AlertmanagerAvailableGrouped alerts, resolved notifications, de-duplication by fingerprint.
Grafana alertingAvailableWebhook contact point.
DatadogAvailableWebhook integration; retries are de-duplicated.

2. Incident management and on-call tools: schedule importers

Read your schedules, rotations and escalation policies from the tool you use today, so you do not rebuild them by hand. The importers need a teams and rotations model first, which is in progress.

ToolStatusWhat it means
PagerDutyPlannedSchedule import with a dry run that shows what cannot be mapped.
OpsgeniePlannedSame shape as PagerDuty. Atlassian has set end of support for Opsgenie for 5 April 2027 (Atlassian blog).
Teams and rotations model (foundation)In progressNeeded before any importer. Not an integration itself.

3. Calendars

Your calendar tells Ackline when you are in a meeting or on leave, which can change how loudly a non-critical alert arrives.

ToolStatus
Microsoft 365 / OutlookPlanned
Google CalendarPlanned

4. IT service management sync

Create or update an incident when an alert arrives and when it is acknowledged, so the record in your ITSM tool and the Ackline audit trail agree.

ToolStatus
ServiceNowPlanned
Jira Service ManagementPlanned

Do you use a tool that is not listed? Say so on the waitlist. The answers decide the order after the alert sources.