Skip to main content
Connect SuperOps so the agent picks up new tickets, gathers context, and either resolves them or hands them back with a plan.

Connect SuperOps

You’ll need an API token and your tenant’s subdomain.
1

Generate an API token in SuperOps

Sign in to SuperOps and go to Settings → My Profile → API Token. Generate a token and copy it. SuperOps shows it only once.
Notes and replies the agent posts appear under the name of the user who owns the token. Create a dedicated user like Rallied or rallied@yourmsp so the ticket history shows which work the agent did.
2

Find your subdomain

Open Settings → MSP Information. Your subdomain is the part before .superops.ai. In acme.superops.ai, the subdomain is acme.
3

Paste both into Rallied

In Rallied, go to Settings → Integrations, find the SuperOps card, and click Connect. Paste the subdomain into Customer Subdomain and the token into API Token, then click Connect.Rallied checks both the US and EU SuperOps regions and connects to the one your tenant is in.
4

Pick which of your clients you want Rallied to work on

Choose the SuperOps clients whose tickets the agent should handle. You can start with one client and add more later.
Rallied sets up the SuperOps webhook for new tickets, ticket updates and customer replies. Rallied verifies every event two ways before an agent sees it. It checks a cryptographic signature from SuperOps and a token unique to your MSP. If you disconnect SuperOps, Rallied removes the webhook subscription from your tenant. The clients you imported stay in Rallied.

What happens when a ticket comes in

When someone opens a ticket in SuperOps for a client you’ve enabled, the agent:
  1. Reads the full ticket and conversation thread.
  2. Looks up the requester in your connected identity provider, such as Microsoft 365, so changes hit the right account.
  3. Posts an internal note with what it understood and what it plans to do.
  4. Does the work, or asks for approval first, depending on your approval settings.
  5. Posts a final internal note with what it did. By default it doesn’t message the requester.
If a workflow matches the ticket, the agent follows it. For sensitive requests such as password resets, MFA changes or admin permission grants, the agent can verify the requester’s identity first. It posts the outcome on the ticket.

Approving an action without leaving SuperOps

When an action needs approval, the agent posts an internal note on the ticket explaining what it wants to do, with Approve and Deny links in the note. Your tech responds in SuperOps. Only the technician assigned to the ticket can approve. Rallied treats replies from anyone else as regular comments, and they don’t move the approval forward.

Internal notes vs. customer replies

In Plan Mode, customer-visible replies are always blocked, even for clients where you’ve enabled them. The agent can write notes in Markdown or HTML. Either way, SuperOps shows them as formatted HTML.

Default approval settings

You can change each default on the SuperOps Policies tab under Settings → Integrations. For anything those actions don’t cover, the agent has a fallback against the SuperOps API. Read-only queries (superops-gql-query) run on Auto. Changes (superops-gql-mutate) need approval by default.

Try it out

1

Open a test ticket in SuperOps

Create a ticket for one of the clients you enabled, with a short subject and description.
2

Watch it in Activity

In Rallied, open Settings → Activity or the client’s Activity tab. The ticket appears within seconds. In Plan Mode, the agent posts an internal note describing what it would do. In Execute Mode, it takes the actions your approval settings allow.
If the ticket doesn’t show up in Rallied, check that:
  • Your subdomain matches your SuperOps URL exactly.
  • The API token hasn’t been rotated in SuperOps since you connected.
  • The test ticket is on a client you enabled when connecting.