Agent Swarm integrations
Agent Swarm connects to the tools a software team already runs: issue trackers, chat platforms, email, CRM, observability, and search. This page is a discovery layer over the documentation, grouping every supported integration by workflow. Each entry links to its canonical setup guide.
Integrations for engineering work
Tickets, pull requests, and review requests become agent tasks, and the work returns to the same place.
GitHub
What enters the swarm: pull request and issue events from a GitHub App webhook: bot assignment, review requests, submitted reviews, @-mentions, or a trigger label.
What agents can do: work the issue or review, push branches, and open pull requests with the gh CLI.
Where results return: comments on the originating issue or pull request, with reactions confirming acceptance and pickup.
GitLab
What enters the swarm: merge request, issue, and comment events from a token-verified webhook, plus CI notification tasks when a pipeline fails on a tracked merge request.
What agents can do: work the issue or merge request with the glab CLI, create merge requests, and comment on issues.
Where results return: notes on the merge request or issue in GitLab.
Linear
What enters the swarm: assigning the Linear agent to an issue creates a swarm task and a Linear AgentSession. A workflow-state gate skips triage and backlog issues by default, with a label override.
What agents can do: post thoughts, actions, responses, and errors back to the AgentSession in real time.
Where results return: activity streams into the AgentSession. Sync is inbound-only: status changes, labels, and comments outside the session go back through the linear-interaction skill, not automatically.
Jira Cloud
What enters the swarm: issues assigned to the bot, or comments that @-mention it, through OAuth 3LO and dynamically registered webhooks.
What agents can do: work the issue with its description and comments read as plain text, and follow up on new mentions.
Where results return: task lifecycle events post back as comments on the linked Jira issue.
Azure DevOps
What enters the swarm: service hooks from Azure Repos. A bot mention in a pull request description or comment creates a task. Azure Repos pull requests only; Azure Boards work items are not supported yet.
What agents can do: clone, push, and open pull requests with git and the az CLI, as a dedicated bot user with its own Personal Access Token.
Where results return: comments on the pull request. As with GitHub and GitLab, anyone who can comment on a connected repository can trigger the swarm.
Set up the Azure DevOps integration
Integrations for team communication
Agents become reachable where people already talk. These are the human-in-the-loop surfaces: assign work, steer it mid-run, approve a decision, and read the outcome in the thread.
Slack
What enters the swarm: @-mentions, slash commands, direct messages, and thread replies, all routed as tasks. A swarm# prefix targets a specific agent or broadcasts to all workers.
What agents can do: run multi-agent workflows across channels and the Slack Assistant sidebar, take steering on running tasks, and route approval requests to a person.
Where results return: replies in the same thread, with configurable reactions tracking the task to completed or failed.
AgentMail
What enters the swarm: email sent to a registered agent inbox. Mail to a worker becomes a task, mail to the lead becomes an inbox message, and thread follow-ups route to the same agent.
What agents can do: read, send, reply to, and forward email through AgentMail's MCP tools, with optional domain filters.
Where results return: email replies in the original thread, from one consistent address.
Kapso (WhatsApp)
What enters the swarm: inbound WhatsApp messages on a provisioned number, delivered through a signed and deduplicated webhook. Each number maps to an agent or a workflow.
What agents can do: reply in-thread over WhatsApp, with the kapso-whatsapp skill for templates, media, reactions, and history.
Where results return: WhatsApp messages to the sender, inside the same conversation.
Composio
What enters the swarm: nothing. Composio is a routed tool layer, not an event source, and the current integration is a prototype and admin surface.
What agents can do: open Tool Router sessions for connected apps such as Gmail, GitHub, Slack, Notion, and HubSpot, generate Connect Links when a user must authorize an app, and execute app tools in the session.
Where results return: tool output goes back to the calling agent or CLI.
Integrations for operations and customer systems
CRM data, Microsoft 365, error monitoring, and web search, inside an agent's reach while it works a task.
Salesforce
What enters the swarm: nothing inbound. Salesforce connects as an MCP server over HTTP, authenticated with OAuth through an External Client App.
What agents can do: call Salesforce's hosted MCP endpoints, such as sObject reads, without managing tokens directly.
Where results return: query results come back to the agent inside the task it is working on.
Microsoft Graph
What enters the swarm: nothing inbound. Microsoft Graph is a reviewed OpenAPI connection using delegated OAuth: a signed-in user authorizes the swarm to act on their behalf.
What agents can do: read and send Teams channel and chat messages, read and send Outlook mail, list OneDrive folders, and read user profiles.
Where results return: data comes back to the agent, and sent messages go out as the authorizing user.
Sentry
What enters the swarm: nothing automatically. Workers ship with sentry-cli pre-installed, and an agent investigates an issue when a task asks it to.
What agents can do: pull issue details, stacktraces, and breadcrumbs with the /investigate-sentry-issue command, then resolve, mute, or unresolve the issue.
Where results return: the issue's status changes in Sentry, and the analysis lands in the task output.
Serply
What enters the swarm: nothing. Serply supplies search access for agent tasks and does not create tasks from incoming events.
What agents can do: request Google web, news, and scholar results through the serply-search skill, using the API key stored in the dashboard.
Where results return: search references come back to the agent, which fetches the linked pages before citing them.
Native integrations vs routed tools
Two kinds of connection matter here. Native event sources create tasks: GitHub, GitLab, Linear, Jira, Azure DevOps, Slack, AgentMail, and Kapso turn webhooks, mentions, assignments, or messages into work. Tool-access surfaces never create tasks: Composio, Salesforce, Microsoft Graph, Sentry, and Serply answer an agent's calls for data or actions while a task runs. Several native sources also emit to the internal event bus, so an event can start an automated workflow instead of an agent task.
How to choose and what you need
Start from where work enters your team. If tickets drive your process, connect an issue tracker first. If conversations drive it, start with Slack, email, or WhatsApp. Then add tool-access surfaces for the systems agents need while they work.
Credentials follow the same split. Native sources need a webhook or app registration: a GitHub App, a GitLab token, OAuth apps for Linear and Jira, a bot PAT for Azure DevOps, Slack Socket Mode tokens, and signing secrets for AgentMail and Kapso. Routed tools need credentials an agent can call with: OAuth for Salesforce and Microsoft Graph, an auth token for Sentry, an API key for Serply, and a project key for Composio. Every permission scope and env var lives in the linked setup guide, and the MCP tools reference lists what agents call once connected. For worked examples see examples, for head-to-head positioning see comparisons, and for plans see pricing. If you would rather not self-host, Agent Swarm Cloud is the managed option.
The full inventory, with setup, behavior, and operational notes for each integration, lives in the integrations documentation.