Before you start
- An owner or admin role in your Ankra organisation, to connect a chat app and change its AI mode. See Roles and access.
- A role that may manage alerts (
alerts.manage), to add a notification destination and change an alert rule. - An alert rule on a cluster. If you have none, add one first: see Alerts.
- Slack: a workspace where you may install apps. Microsoft Teams: Ankra AI allowed in your tenant. If your tenant restricts Store apps, your Teams administrator allows it once; Connecting Microsoft Teams has a message to send them.
- For the CLI steps: the Ankra CLI, signed in.
1
Connect your chat app
- Slack
- Microsoft Teams
Open Ankra AI → Gateway connections (Ankra says The Slack workspace is connected., and the workspace shows as a row in the Slack section.
/next/ai/settings/gateway). In the Slack section, press Add to Slack, approve the app in Slack, and come back.ankra slack status lists it too.2
Link your account and let Ankra AI act
Mention the bot once in any channel it is in (@Ankra in Slack, @Ankra AI in Teams), press Connect Ankra account in its reply, and sign in. Its next answers run with your own Ankra permissions.Then, on the workspace’s or tenant’s row on Gateway connections, switch the AI mode from Ask to Agent. The row is now marked Can act.
3
Add the channel as a destination
- Portal
- CLI
Open Integrations & alerts → Notification destinations (
/next/organisation/notification-destinations) and press Add destination.- Set Kind to Slack or Microsoft Teams.
- Under How Ankra posts, choose To a channel, then pick the Channel.
- Give it a Name, such as
on-call, and press Add destination.
4
Send an alert to the channel
- Portal
- CLI
Open Integrations & alerts → Alert rules, open the rule’s options menu and press Change…. Under Tell these destinations, tick
on-call and press Save.The alert now goes to the channel each time the rule fires. To send every alert there instead, add a routing rule on Integrations & alerts → Notification routes: press Add rule, choose A destination under Send to and pick on-call, choose Only these kinds and tick Alert firing, then press Add rule.5
Ask Ankra AI in the alert's thread
When the alert fires, its card arrives in the channel with Acknowledge and Snooze 1h. Reply in the card’s thread and mention the bot, for example:Ankra AI reads the thread it was mentioned in, so it starts from the alert you are looking at. In Slack it reads up to 50 of the thread’s replies the first time it is mentioned there; in Teams the app reads the thread from version 1.1.0. Say
use cluster <name> to point the thread at one cluster. Its answer is visible to everyone in the channel, and you can follow up in the thread without mentioning it again in Slack.6
Approve the fix from chat
When Ankra AI proposes a change, the bot posts a Confirmation needed card with Confirm and Deny. Read what the card says it will change, then press Confirm. A decided card is replaced by its outcome.Only the person who asked can decide the card. If the cluster changed in the meantime, the card shows what moved and offers Confirm anyway.Fixes that Ankra AI starts on its own, from an alert, follow the level on Ankra AI → Autonomy and approvals. With Ask first, every fix waits for an organisation admin to approve or deny it, on a card the approvals Slack webhook posts with Approve and Deny, or in Needs you. See AI Autonomy.
Verify
- The alert’s card in the channel reads its outcome where Confirm was.
- Open Identity & access → Audit log (
/next/organisation/audit). The change is recorded under your name, not the bot’s. - Run
ankra alerts routes preview --kind alert_trigger_firedagain. The channel is still where a firing alert goes.
What can go wrong
More answers for each chat app are in AI Connections.
Where to go next
- Notification routing - send other notifications, such as failed pipelines, to the same channel, or one channel per project.
- AI Autonomy - choose which fixes Ankra AI may run on its own and which wait for a person.
- Set up the AI Gateway - connect pull requests and email alongside chat.