Connect your monitoring stack
Akmatori has built-in webhook adapters for five monitoring tools, plus messaging connectors for Slack (alert intake and notifications) and for Telegram and Discord (notifications only). You set up all of them on the Connectors page.
Supported integrations
Alertmanager
Receive alerts from Prometheus Alertmanager
Zabbix
Receive Zabbix alerts; the agent can query hosts, problems and history
PagerDuty
Receive PagerDuty webhooks; the agent can look up incidents and on-call
Grafana Alerting
Receive Grafana alerts; the agent can query dashboards, data sources and alert rules
Datadog
Receive alerts from Datadog monitors
Slack channels
Turn alert messages in Slack channels into incidents and reply in the thread
Webhook adapters cover Alertmanager, Zabbix, PagerDuty, Grafana Alerting and Datadog. Each webhook belongs to a connector. The Zabbix, Grafana and PagerDuty connectors also hold the API access that the agent uses to query those tools during an investigation. Slack is a messaging connector with one or more Channels. A Slack channel can post results, listen for alert messages from bots (and, if you turn it on, from people), and receive cron job output.
When an incident starts from Slack, Akmatori adds an hourglass reaction to the alert message while the agent works. If your Slack app has the AI Assistant feature, the thread also shows the agent's latest step as a status line. When the run ends, Akmatori posts a summarized result as a thread reply.
Alert sources and cron jobs can target a specific notification Channel. A Slack channel gets the full Slack flow (status in the thread, summarized result). A Telegram or Discord channel gets the alert and then the investigation result as a reply; these providers only post and do not listen. If an alert source has no channel, its alerts go to the Slack channel marked Default post target.
Each alert source can have its own webhook secret. Send it in the header that the adapter checks: X-Alertmanager-Secret, X-Grafana-Secret, X-Datadog-Signature or DD-API-KEY, X-Zabbix-Secret, or a PagerDuty v3 signature in X-PagerDuty-Signature. All adapters except Zabbix also accept Authorization: Bearer <secret>.
How integrations work
1. Webhook endpoints
Each alert source gets its own webhook URL, /webhook/alert/<uuid>. Your monitoring tool sends alerts to it.
2. Alert normalization
The adapter converts each alert to one common format and stores it as an event. Only events classified as alerts open or join Incidents; change and info events are stored without an investigation.
3. Investigation
The agent investigates the incident with your Skills, Runbooks, Memory and Connector tools. Risky actions become proposals that wait for your approval.