Skip to main content
Integrations give your Rallied agent real capabilities. Without them, the agent can diagnose a ticket but cannot resolve it. When you connect an integration, the agent gains a set of tools: add a note to a ConnectWise ticket, reset a Microsoft 365 password, run a NinjaOne script, look up a runbook in IT Glue. It uses them automatically as part of resolving helpdesk requests.

​
How integrations work

When an employee submits a ticket or sends a message to the agent, the agent diagnoses the issue and selects the right tools to resolve it. Each tool corresponds to an API action in one of your connected integrations. The agent calls those tools on your behalf, logs every action, and routes any sensitive operations through your approval flow before executing. Credentials are never stored on your agent servers. OAuth tokens and API keys are managed securely and transmitted to the agent only at runtime via the Tool Gateway. After you connect an integration, Rallied automatically:
  • Syncs the available tools from that integration into your agent’s tool catalog
  • Seeds sensible default policies for each tool (read-only actions run automatically; write actions require approval)
You can override any default policy from the integration’s detail page — open it from MSP Settings → Integrations.

​
Connecting via OAuth

For integrations that use OAuth, the flow is the same every time:
1

Open the Integrations tab

Navigate to MSP Settings → Integrations.
2

Click Connect

Find the integration you want to connect and click the Connect button.
3

Authorize in the provider

A login window opens in the provider’s own interface (Atlassian, Slack, Microsoft, etc.). Sign in and grant the requested permissions.
4

Tools are synced automatically

Once authorized, Rallied fetches the available tools and seeds default policies. The integration shows as Connected and the agent is ready to use it.
Some integrations use a credentials form instead of OAuth redirect. For those, you enter your API credentials (URL, keys, tokens) directly in Rallied.

​
Approval flows

Every integration that can take write actions participates in the approval flow. When the agent’s plan includes an action you’ve marked as needing approval, it posts an approval request through one of your connected approval channels:
  • ConnectWise Manage — a note is added to the ticket
  • HaloPSA — an action is created on the ticket
  • Autotask — a note is added to the ticket
  • Jira — a comment is posted on the issue (where Jira is connected)
  • Slack — a DM is sent to the assigned technician (where Slack is connected)
Technicians can approve or deny directly from those channels. You don’t need to open Rallied.

​
Available integrations

Slack

Business messaging. Gives the agent a bot presence in your client’s Slack workspace for employee interaction and approval notifications.

Jira

Ticketing by Atlassian. The agent creates and updates Jira issues, receives new tickets via webhook, and posts approval requests as comments.

ConnectWise Manage

PSA platform. The agent receives new service tickets, posts notes, and routes approvals through ConnectWise.

HaloPSA

ITIL-aligned PSA. The agent receives HaloPSA tickets, posts actions, and routes approvals through HaloPSA.

SuperOps

Unified PSA and RMM. Rallied’s agents triage, work, and resolve SuperOps tickets. Your team approves the actions you’ve flagged for review.

MCP Servers

Custom tool servers. Connect any server that implements the Model Context Protocol to extend the agent with your own tools.

​
Identity & access

​
PSA / ticketing

​
RMM

​
Security & EDR

​
Email security

​
Documentation & knowledge

See Documentation for how the agent uses these sources together.

​
CRM & business

​
Communication

​
Scheduling

Don’t see an integration you need? You can connect any tool that implements the Model Context Protocol via MCP Servers.