Skip to main content
Triggr works with Zorus customers, groups, policies, deployment tokens, endpoints and unblock requests. The API token acts as one Zorus user, so Triggr can see and do only what that user can.

​
Set up Zorus

You need a Zorus Portal user with the System Administrator permission.
1

Choose the user to impersonate

Under Users > User Management, pick a user whose permissions cover the customers and endpoints your workflows use. Zorus’s Portal Permissions Matrix lists what each permission covers.
2

Generate an API token

In the Zorus Portal, go to Integrations > API Access and click Generate API Token. Select the user, name the token Triggr, generate it and copy it. Zorus won’t show it again. See Zorus’s API QuickStart.

​
Connect it in Triggr

1

Open the configuration

Go to Integrations > Zorus 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

Paste the token alone into apiKey, without Impersonation in front, and click Save Configuration.
The Zorus configuration window with an apiKey field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
There’s no client mapping: one token covers every customer the user can access. Workflows identify a customer by the Zorus UUID from Search Customers, and search actions take a JSON filter such as {"nameContains": "Contoso"}.

​
Troubleshooting

Check apiKey holds only the token, and the token is still enabled under Integrations > API Access and hasn’t been rotated or deleted. Rotate Token revokes the old value at once, so paste the new one into Triggr straight away.
Check the impersonated user’s permissions and assigned customers, or generate a token for a different user.
Zorus allows 100 API requests a minute per account, shared by everything using it. Spread large workflows out or run them in smaller batches.