Skip to main content
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 and its API reference.

​
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.
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.
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

SuperOps rejected the token, perhaps because it was regenerated. Generate a new one and paste it into apiKey.
customerSubDomain must be the subdomain alone, without https:// or .superops.ai, and the account must be hosted in SuperOps’s US data centre.
SuperOps reports query problems in body.errors in the step’s output. Check the query and variables against the API reference.
If IP Restrictions is on in Settings > Security Management, add Triggr’s IP addresses to the allowed ranges.