Skip to main content
Triggr works with DNSFilter organisations and their users, networks, policies, roaming clients and reports.

​
Set up DNSFilter

1

Add a dedicated user for Triggr

In the DNSFilter MSP dashboard, go to MSP > Users and select Add User. Leave Organization Access Restrictions blank so Triggr can reach every organisation, then accept the invitation DNSFilter emails from @netalerts.io. If your MSP account uses single sign-on, add the user through your SSO configuration instead.
2

Create an API key as that user

Signed in as the Triggr user, go to Account Settings > Security > API Keys and select + Create Key. Enter a Name and Expiration, select Generate Key, copy the key, then select Save. DNSFilter shows the key only once, and doesn’t warn you before it expires.
See DNSFilter’s API Keys and user permissions guides.

​
Connect it in Triggr

1

Open the integration

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

Paste the key

Paste the key (it starts with eyJ) into ApiKey, with nothing such as Bearer in front, then click Save Configuration.
The DNSFilter configuration window with an ApiKey field, 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 DNSFilter organisation in Mapped to for anyone left. Triggr saves each match as the client’s organizationId variable, so pass {{ ctx.client.organizationId }} to any action that asks for an organisation ID.
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.

​
Troubleshooting

The key has expired or been revoked, or ApiKey has spaces or Bearer in it. As the Triggr user, check the key’s Status under API Keys.
Keys can’t be extended. As the Triggr user, create a new key, paste it in via Edit on the Base Configuration card, then revoke the old key. Only the user who created a key can revoke it.
The Triggr user’s role doesn’t allow the change, or it has Organization Access Restrictions. Fix both in MSP > Users, then click Refresh on Client Mapping.
Each user can have five active keys. Revoke or delete keys the Triggr user no longer needs, then try again.
DNSFilter allows 2,000 requests per 300 seconds per organisation, including dashboard use. Run large bulk workflows in smaller batches.