Aira connects to third-party services to pull context and push updates. Configure integrations from Settings → Integrations.
GitHub
Connecting
Provide a Personal Access Token (PAT) with repo access. Aira stores the token encrypted in the database.
What it unlocks
- Repository analysis — Aira clones your repo (ephemeral, depth-1), extracts tech stack, architecture patterns, API surface, dependencies, and recent activity. Only the structured analysis is stored, never raw source code.
- PR tracking — Pull requests are linked to Aira tasks via branch name conventions (
task/TASK-ID-description), PR body mentions ("Closes TASK-xxx"), or manual linking. - Webhook events — GitHub events (PR opened, merged, closed) can trigger status updates in Aira.
- AI convention file scanning — Aira detects
AGENTS.md,CLAUDE.md, and similar convention files in your repo to understand project coding standards.
Extracted information
| Category | What Aira learns |
|---|---|
| Tech stack | Languages, frameworks, runtime versions |
| Architecture | Directory structure, entry points, module boundaries |
| API surface | REST endpoints, GraphQL schemas, CLI commands |
| Dependencies | From package.json, pyproject.toml, go.mod, etc. |
| Patterns | Auth approach, database layer, testing framework, CI/CD |
| Recent activity | Last N commits, active contributors |
Auto-status updates
When a PR is merged, the linked task moves to done. When all tasks under a feature are complete, the feature moves to shipped.
Bitbucket
Connecting
Provide your Bitbucket workspace and an app password with repository read access.
What it unlocks
- Repository analysis — Same as GitHub: ephemeral clone, structured extraction
- PR automation — PR events linked to tasks, auto-status updates on merge
- Webhook events — Bitbucket webhook events trigger task status transitions
Jira
Connecting
Provide your Jira instance URL and an API token. Aira uses this to read ticket data.
What it unlocks
- Import Jira tickets as sources for analysis
- Two-way sync concepts (planned): task status changes in Aira can reflect in Jira and vice versa
Slack
Connecting
Provide a Slack Bot Token with appropriate permissions. Link a Slack channel to your Aira project.
What it unlocks
- Notifications — Aira posts updates to the linked Slack channel (task completions, sprint starts, risk alerts)
- Channel linking — Associate a Slack channel with your project for automated updates
- Bot interaction — The Slack bot can respond to queries about project status
Telegram
Connecting
- Navigate to Settings → Integrations and click Connect for Telegram
- Aira generates a deep-link URL to the Telegram bot
- Open the link in Telegram and tap Start
- The bot verifies your identity and binds your Telegram chat to your Aira project
What it unlocks
- Chat with Aira — Send messages to the Telegram bot and interact with Aira directly. Ask about project status, request task updates, or discuss features. The bot processes your messages through the same multi-agent pipeline as the web chat.
- Rich formatting — Agent responses are rendered as Telegram HTML with support for bold, italic, strikethrough, blockquotes, bold+italic, inline code, and code blocks. Long responses are automatically chunked without breaking HTML tags.
- Typing indicator — The bot shows a typing indicator while the agent processes your message, so you know it's working.
- Project switching — Use the
/projectscommand to switch between your Aira projects within Telegram - New threads — Use the
/newcommand to start a fresh conversation thread - Notifications — Receive project updates, task completions, and alerts in your Telegram chat
- Full context — The bot has access to your project's knowledge ledger, so conversations are grounded in real project data
Auto-refresh after binding
After completing the deep-link binding flow, the Settings page automatically refreshes the Telegram integration status. No manual page reload needed.
Environment setup (self-hosting)
If you're self-hosting Aira, you need to configure:
AIRA_TELEGRAM_BOT_TOKEN— Your bot token from @BotFatherAIRA_TELEGRAM_BOT_USERNAME— The bot's usernameAIRA_TELEGRAM_WEBHOOK_SECRET— Shared secret for webhook verification
Webhook events
When integrations are configured, certain actions in Aira can trigger outbound webhooks:
- Sprint started / completed
- Task status changed
- Feature shipped
- Risk detected
- Heartbeat alert
Webhook payloads include the relevant entity data and project context. Aira includes replay protection — each webhook delivery carries a unique ID, and duplicate deliveries are rejected via a database-backed receipt ledger.