In this article
The DNSFilter app in Zapier connects DNSFilter to other applications so DNS activity can trigger automated actions, and other applications can make changes in DNSFilter. Zapier is available on DNSFilter Plus plans and above and requires a Zapier subscription. See Zapier's pricing page to choose a Zapier plan.
Accounts on legacy Pro plans retain access to features included in their plan. New features released after the Plus plan launch may be available on the Plus plan only.
How DNSFilter works with Zapier
Zaps use two kinds of building blocks:
- Triggers: Activities that start a series of automations. To apply a zap to an entire DNSFilter account, leave the Organization and Site fields blank on any trigger.
- Actions: Automated tasks, such as sending a Slack message, recording a row in a cloud spreadsheet, or adding a domain to a DNSFilter Block List.
The DNSFilter app in Zapier has the following triggers and actions.
Triggers
- Dynamic Hostname Not Resolving
- Blocked Page Visited
- Blocked Page Form Submitted
- Policy Changed
- Invoice Available
- Account Activity Occurred, such as:
- Organization added or deleted
- Site added or deleted
- Roaming Client added or deleted
- Roaming Client uninstalled or reactivated (Windows only)
- Relay added or deleted
- Administrator added or deleted
- MFA enabled or disabled
Actions
- Create Organization
- Create Site
- Allow Category in a Policy
- Block Category in a Policy
- Assign Policy to a Site
- Assign Policy to a Roaming Client
- Add to Allow List
- Add to Block List
Zap examples
Zapier lists ready-made DNSFilter templates on the DNSFilter integrations page. Common uses include:
Create a ticket from an unblock request
MSPs and internal IT departments often send user requests to a ticketing system. When a user reaches a website blocked by policy, the Block Page shows that access is forbidden. The user can fill out a form explaining why they need access to the site. A zap can turn that submission into a ticket.
Notify when users are blocked from phishing, malware, and botnets
DNSFilter detects and prevents access to botnets, phishing, and malware across all devices. An alert when users are blocked from these threats helps admins remediate devices and educate users.
Onboard a new customer in DNSFilter
Connect back-office processes to DNSFilter onboarding. From Salesforce or a similar CRM tool, trigger setup of a new Organization and Site in DNSFilter. The zap assigns a Filtering Policy and can send a notification in Slack or by email when the process completes.
Unblock requests from authorized users
Some users, such as teachers or senior employees, are trusted to add exceptions to Filtering Policies. Instead of routing every request through help desk tickets, a zap can enable these users to process requests on their own.
Alert when a dynamic DNS hostname is not resolving
Smaller networks and mobile or LTE networks can use dynamic DNS so that DNSFilter can track changes to the external IP address. A zap can send a notification when DNSFilter detects a problem with a dynamic DNS hostname, giving early notice of downtime.
Alert on administrator account or MFA changes
A zap can send an alert when important account access events happen in DNSFilter, such as an administrator account being deleted or account protection being reduced. Use any notification method, such as Slack, PagerDuty, or email.
Comments
0 comments
Article is closed for comments.