Skip to main content
Triggr reads Auvik sites, devices, networks, configuration backups, alerts, statistics, SNMP pollers, billing usage and SaaS Management data, and dismisses alerts.

​
Set up Auvik

You need a mailbox for a dedicated Triggr user in Auvik. If Auvik uses Single Sign-On for All Users, the user must also exist in your identity provider.
1

Choose a role

The built-in API Access Only role covers most actions. For Dismiss Alert or SNMP pollers, go to Manage Users > Roles > Add Role on your multi-site dashboard, tick API Role Only and select the permissions you need. Don’t use Read Only, which has no API permissions.
2

Invite a Triggr user

In Manage Users, click Invite User and enter an address such as triggr@yourcompany.com. Select every site Triggr should work with, give the user the role on each and click Invite. Authorise the user on sites you add later, too.
3

Generate an API key as that user

Accept the invitation and sign in as the Triggr user (only users can generate their own keys). Click the username in the side navigation bar, click Generate API Key and copy the key. Auvik shows it only once.
4

Find your region

It’s the three characters before my.auvik.com in your Auvik address, such as us2 in https://yourcompany.us2.my.auvik.com.
See Auvik’s API access only role article.

​
Permissions

API Access Only includes every permission below except the last two rows. The SaaS Management actions also need an Auvik SaaS Management subscription.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > Auvik 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 credentials

Enter the API Key, choose your Region, enter the Triggr user’s sign-in email address as Username, then click Save Configuration.
The Auvik configuration window with an API Key field, a Region drop-down and a Username field, each with a hint, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

​
Map your clients

On the Client Mapping card, click Apply 100% Matches, then choose the Auvik site in Mapped to for anyone left. A client can map to several sites. Multi-sites aren’t listed, and sites are named by their domain prefix (acme in acme.us1.my.auvik.com), so short prefixes may need mapping by hand.
The Client Mapping card with All, Mapped and Unmapped filters, Acme Corp mapped to Acme Corp with a 75% suggested mapping, and Globex unmapped with a Select ConnectWise Manage clients dropdown.

The Client Mapping card, shown here for ConnectWise Manage as an example.

Triggr saves the mapping as the client’s auvikTenantId, auvikTenantIdCsv and auvikTenantIdList variables. Pass {{ ctx.client.auvikTenantIdCsv }} as tenants on list and statistics actions, or {{ ctx.client.auvikTenantIdList[0] }} where an action takes one tenantId. To follow links.next to the next page of results, use a Generic Integration Action step with URL Type set to Absolute URL.

​
Troubleshooting

Check Username is the full sign-in email, the key hasn’t been regenerated, and Region matches your Auvik address, which Auvik occasionally moves. Verify Credentials returns 200 when the username and key are valid.
The role lacks the action’s permission, or the user isn’t authorised on every site in tenants. After a rate limit, Auvik can also return 403 until its five-minute window resets.
Authorise the Triggr user on the site with a role that includes API - Tenants, then click Refresh on Client Mapping. Map clients to the sites under a multi-site, not the multi-site.
Auvik allows 2,500 API requests in five minutes. Spread workflows that loop over many clients or pages out over time.
Ask for fewer tenants per call, a smaller page, and a shorter time range or coarser interval.