Skip to main content
Connect ConnectWise Manage so the agent picks up new service tickets and either resolves them or hands them back with a plan.

Before you connect

Rallied signs in to ConnectWise using an API member you create. Give that member a dedicated security role so its access covers only what Rallied needs. The security role sets the most Rallied can access. Your approval settings decide which actions it actually runs.

Create the “Rallied” security role

In ConnectWise, go to System → Security Roles and create a new role called Rallied. Configure the role with the permissions below. Read access. Set Inquire Level to All (all entries) for these modules. Read access never changes anything in ConnectWise. Write access. Set Add Level and Edit Level to All for these entries.
Manage Attachments lets Rallied attach files to tickets, such as a screenshot a user shares in a chat. Without Add: All on this entry, attachments fail with a “You do not have security permission to perform this action” error.
Delete access. Grant one entry only. Rallied registers a webhook when you connect and removes it when you disconnect. Without delete access here, disconnecting leaves an orphaned callback firing at Rallied.
Leave everything else read-only. Keep Add, Edit, and Delete at None for anything not listed above. That includes Finance write entries (Invoicing, Agreements, Billing Rate Maintenance, Accounting Interface), Procurement write entries (Purchase Orders, Purchasing Approvals, Products), Project entries, Sales, Marketing, and the sensitive System entries (Member Maintenance, Security Roles, Add Licenses).This is the least-privilege configuration for what Rallied writes today. To have the agent work in a new area later, see Granting more later.

Granting more later

Rallied also ships generic ConnectWise API tools (GET, POST, PATCH to any endpoint). By default they’re Disabled or set to Approval needed. To have the agent work in areas the role doesn’t cover, such as projects, agreements or purchase orders:
  • Grant those entries in the ConnectWise security role.
  • Enable the corresponding tools in your approval settings.

How to connect

1

Create an API member

In ConnectWise Manage, go to System → Members → API Members and create a new API member.Under that member, create a new API key pair. Note the Public Key and Private Key. ConnectWise shows the private key only once.
2

Optional: map your technicians to ConnectWise members

ConnectWise doesn’t let API-only members create time entries. Time has to be attributed to the technician who did the work. To attribute notes and time entries to your technicians:
  • Create a regular (non-API) member for each technician under System → Members.
  • Map them in Rallied under Settings → Integrations → ConnectWise → member mappings.
Rallied still authenticates with the API member’s keys. Rallied uses the mapped members only as the author of notes and time entries.
3

Open the ConnectWise Manage card

In Rallied, go to Settings → Integrations, find the ConnectWise Manage card, and click Connect.
4

Enter your credentials

5

Connect and confirm

Click Connect. Rallied validates the credentials, registers a webhook in ConnectWise, and imports your existing companies as clients. Each new client gets an agent automatically. The card shows Connected when complete.

What happens when a ticket comes in

When a new service ticket is created in ConnectWise, Rallied picks it up right away.
  1. The agent posts an internal note with what the ticket is about, who it’s from, and what it plans to do.
  2. Actions set to Auto, such as looking up context or drafting a response, run without waiting.
  3. Actions that need approval wait for a technician. See Approving actions without leaving ConnectWise.
For sensitive requests such as password or MFA resets, the agent can verify the requester’s identity first. It posts the outcome as an internal note.

If Rallied missed the ticket when it was created

ConnectWise announces a new ticket only once. Rallied can miss that first announcement in these cases:
  • The ticket’s company wasn’t yet mapped to a Rallied client.
  • The ticket’s status wasn’t one of the accepted statuses at creation time.
  • ConnectWise was temporarily unreachable when Rallied went to fetch the ticket.
You don’t need to do anything to recover. When a later note or update lands on the ticket and the client and status now qualify, Rallied starts the agent at that point. The agent picks the ticket up from its current state, including the note that triggered it.

Approving actions without leaving ConnectWise

When an action needs approval, the agent posts an internal note on the ticket describing what it plans to do. Reply to that note to approve or deny. You choose which actions need approval on the ConnectWise Manage Policies tab under Settings → Integrations. Rallied classifies the intent of the reply. It ignores a neutral reply, such as a status update or a comment for another tech, so that reply won’t approve or deny anything.

Internal notes vs. customer-visible replies