Skip to main content
The Connections section under AI → Settings → Connections gathers every integration the AI communicates through, in four groups.

​
Chat & Notifications

  • Slack - install the Ankra app into your workspace with Add to Slack. Once connected, the AI can hold conversations in channels, send approval requests, and post to the home channel chosen under Workspaces.
  • Microsoft Teams - connect your tenant and add the Ankra bot to the teams that should reach the AI. See Connecting Microsoft Teams below.
Each connection carries its own AI mode (what the AI may do when talked to from that surface), defaulting to the organisation-wide mode set under Workspaces.

​
Connecting Microsoft Teams

The Ankra AI app is not in the Microsoft Teams app store yet, so the bot is installed from an app package:
1

Download the app package

On the Microsoft Teams card under Connections, click Download the Teams app package (a small .zip containing the app manifest and icons).
2

Upload it to Teams

In Microsoft Teams, open Apps → Manage your apps → Upload an app → Upload a custom app and pick the downloaded .zip. If custom app uploads are disabled in your tenant, a Teams administrator can publish the package to your organisation’s app catalog instead (Teams admin center → Teams apps → Manage apps → Upload new app).
3

Add the bot and claim your tenant

Add Ankra AI to a team, group chat, or personal scope. When it is first added it posts a one-time claim code. Paste that code into the Connect a tenant field on the Teams card - this requires organisation admin and binds the Teams tenant to your Ankra organisation.
4

Route alerts to a channel

Once the bot is in a team, alert Destinations offer a channel picker for Teams the same way they do for Slack: pick Team / Channel instead of pasting a Power Automate URL, and the bot posts the Adaptive Card itself. Add the bot to every team whose channels you want to route to.
For alert cards in Teams without the bot, use a webhook destination with the Adaptive Card template instead - see Microsoft Teams webhooks.

​
Source Control

Connect GitHub (via the Ankra GitHub App) or GitLab so the AI can read repositories, comment on pull requests, and power PR preview environments.

​
MCP Tool Servers

Register your own MCP servers to give agent runs extra tools. Each server exposes its tools after a health probe, and every tool needs an explicit role grant before runs can call it - registering a server grants nothing by itself.

​
Outbound Delivery

  • Destinations - webhook endpoints that receive platform events, with ready-made templates for Slack, Teams, Discord, and PagerDuty, or a custom JSON payload template. Send a test delivery from the destination’s menu to verify the wiring. See the webhook guide for payloads and templates.
  • Notification routes - rules that decide which events (alerts, security findings, agent status, GitOps) go to which destination. Events with no matching route fall back to the home channel.

​
Permissions

Connecting, disconnecting, and changing destinations or routes requires organisation admin.