> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SuperOps (US)

> Connect SuperOps to Triggr with a SuperOps API token and your SuperOps subdomain.

Triggr lists SuperOps tickets and runs any query or mutation in SuperOps's GraphQL API, through SuperOps's US data centre at `api.superops.ai`. It acts as the user whose token you use.

## Set up SuperOps

**1. Generate an API token**

Sign in as the user Triggr should act as, go to **Settings > Your Profile > API token**, click Generate Token and copy it. Each user has one token, and generating a new one replaces it.

**2. Find your subdomain**

Go to **Settings > Company information** and copy your subdomain.

See SuperOps's guide to [using its GraphQL APIs](https://support.superops.com/en/articles/6632215-how-to-integrate-applications-using-superops-ai-graphql-apis) and its [API reference](https://developer.superops.com/msp).

## Connect it in Triggr

**1. Open the configuration**

Go to **Integrations > SuperOps (US)** and click **Configure** on the Base Configuration card.

![The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**2. Enter the token and subdomain**

Paste the token into apiKey, enter your subdomain alone as customerSubDomain, such as `yourcompany`, and click Save Configuration.

![The SuperOps (US) configuration window with empty apiKey and customerSubDomain fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/rFRD51HB_88hTzdJ/images/superops/configure.png?fit=max\&auto=format\&n=rFRD51HB_88hTzdJ\&q=85\&s=01e48cb193f1079edcb9a6fb6d1da552)

One connection covers all your clients. Execute GraphQL Query sends graphQlQuery as the whole request body, so enter JSON with a `query` (and `variables` if needed), not the query text alone.

## Troubleshooting

> [accordion] integration request failed with status code: 401
>
> SuperOps rejected the token, perhaps because it was regenerated. Generate a new one and paste it into apiKey.

> [accordion] Requests fail although the token is right
>
> customerSubDomain must be the subdomain alone, without `https://` or `.superops.ai`, and the account must be hosted in SuperOps's US data centre.

> [accordion] The step succeeds but returns errors
>
> SuperOps reports query problems in `body.errors` in the step's output. Check the query and variables against the [API reference](https://developer.superops.com/msp).

> [accordion] Requests are blocked by IP restrictions
>
> If IP Restrictions is on in Settings > Security Management, add [Triggr's IP addresses](https://kb.mspprocess.com/security/ip-allowlist.md) to the allowed ranges.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.