Integration
Connect DNSFilter and PDQ Connect
When Blocked Page Form Submitted fires in DNSFilter, your agent runs Add group in PDQ Connect, or New Deployment in PDQ Connect to Add organization user in DNSFilter. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want DNSFilter and PDQ Connect to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What DNSFilter and PDQ Connect can do together
From DNSFilter to PDQ Connect
When Blocked Page Form Submitted in DNSFilter
then Add group in PDQ Connect
When Policy Changed in DNSFilter
then Create Custom Field in PDQ Connect
From PDQ Connect to DNSFilter
When New Deployment in PDQ Connect
then Add organization user in DNSFilter
When New Device in PDQ Connect
then Add IP address in DNSFilter
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with DNSFilter and PDQ Connect
Triggers and actions 13 triggers · 47 actions
Trigger
Blocked Page Form SubmittedTriggers when a user submits the form on the blocked page.
Trigger
Blocked Page VisitedTriggered when someone in your DNSFilter account hits a blocked page.
Trigger
Invoice AvailableTriggered when a new DNSFilter invoice becomes available.
Trigger
Policy ChangedTriggered when a DNSFilter policy is created or changed.
Action
Add IP addressAdds an IP address to a DNSFilter site (network) so DNS traffic from that address is filtered under the site's policy.
Action
Add organization userAdds a new or existing user, by email, to a DNSFilter organization with the chosen role.
Action
Add policyCreates a new DNS filtering policy in a DNSFilter organization, with its allow/block lists, blocked categories and safe-search settings.
Action
Add scheduled reportCreates a scheduled report that emails DNSFilter traffic and threat summaries for an organization on a recurring schedule.
Action
Add to Allow ListAdds a single domain to a DNSFilter policy's allow list, with a note explaining why.
Action
Add to Block ListAdds a single domain to a DNSFilter policy's block list, with a note explaining why.
Action
Allow Category in a PolicyAllows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.
Action
Assign Policy to a Roaming ClientAssigns a DNSFilter policy to a roaming client, so that device filters against that policy.
Action
Assign Policy to a SiteAssigns a DNSFilter policy to a site, so traffic from that site filters against that policy.
Action
Block Category in a PolicyBlocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.
Action
Create OrganizationCreates a new organization under an MSP in DNSFilter.
Action
Create SiteCreates a new site (network) in DNSFilter, optionally on a chosen policy and block page.
Action
Delete IP addressRemoves an IP address from your DNSFilter account.
Action
Delete organization userRemoves a user from a DNSFilter organization. The user's account itself is not deleted.
Action
Delete policyDeletes a policy from your DNSFilter account.
Action
Delete siteDeletes a site (network) from DNSFilter. A site with active roaming clients or LAN proxies cannot be deleted.
Action
Find domain by FQDNReturns the domain DNSFilter has on record for a fully qualified domain name, including its host, name and associated categories and applications.
Action
Find query logsReturns DNS query log entries for a time period, filtered by domain, FQDN, network, roaming client, user, policy, category or result (allowed/blocked).
Action
Get organizationReturns the details of one DNSFilter organization by its ID, including its name, billing contact, feature flags and associated networks. An error occurs if the organization is not found.
Action
Get policyReturns a DNSFilter policy by ID, including its allow and block lists, blocked categories and safe search settings. An error occurs if the policy is not found.
Action
Get siteReturns a DNSFilter site (network) by its ID, including its name, address, block page settings and linked policies.
Action
List categoriesReturns every DNSFilter content category, including internal categories, with each category's name, description and whether it is a security threat.
Action
List IP addressesReturns the IP addresses associated with your DNSFilter account, optionally narrowed by a search term.
Action
List organizationsReturns all organizations your DNSFilter account can access, optionally filtered by name, type or MSP.
Action
List organization usersReturns the users of a DNSFilter organization, with their contact details, role and organization access.
Action
List policiesReturns every DNS filtering policy your DNSFilter account can access, with each policy's allow list, block list and settings.
Action
List sitesReturns the sites (networks) in your DNSFilter account, optionally filtered by a search term or by whether a policy is assigned.
Action
Update organizationUpdates an organization's name, billing contact, address, plan and privacy settings, and returns the updated organization.
Action
Update policyUpdates a DNSFilter policy's name, safe-search settings, allow/block lists, blocked categories, countries and applications.
Action
Update siteUpdates a site's name, organization, policies, block page, address, IP addresses and local DNS settings, and returns the updated site.
Trigger
Matching Custom FieldTriggers for each PDQ custom field matching your filters on each poll, including ones that already exist.
Trigger
Matching DeploymentTriggers for each PDQ deployment matching your filters on each poll, with its status counts as first seen.
Trigger
Matching DeviceTriggers for each PDQ device matching your filters on each poll, including devices that already exist.
Trigger
Matching GroupTriggers for each PDQ group matching your filters on each poll, including groups that already exist.
Trigger
Matching PackageTriggers for each package in your PDQ library matching your filters on each poll, including existing ones.
Trigger
New DeploymentTriggers when a new deployment is created in PDQ.
Trigger
New DeviceTriggers when a new device is enrolled in PDQ.
Trigger
New GroupTriggers when a new device group is created in PDQ.
Trigger
New PackageTriggers when a new package is added to your PDQ library.
Action
Add groupCreates a static device group in PDQ Connect, optionally adding devices to it.
Action
Clear device custom field valueClears the value of a custom field on a device. The custom field itself is not deleted.
Action
Create Custom FieldCreates a new custom field definition in PDQ that devices can hold a value for.
Action
Delete custom fieldDeletes a custom field definition and removes its values from all devices.
Action
Delete groupDeletes a static group in PDQ Connect. The devices in the group are kept; only their membership is removed.
Action
Deploy PackageDeploys a package version to the PDQ devices and/or groups you list.
Action
Find Deployment by IDReturns one PDQ deployment by its ID with its current task status counts.
Action
Find DeviceFinds the first device in your PDQ organization whose name or hostname matches. Use ^value for starts-with or ~value for contains.
Action
Find Device by IDReturns one device in your PDQ organization by its ID, with its hardware, OS, user and network details.
Action
Find Device GroupFinds the first device group in PDQ whose name matches.
Action
Find Device VulnerabilitiesReturns the vulnerabilities detected on one PDQ device, optionally filtered by status or risk score.
Action
Find PackageFinds the first package in your PDQ library whose name or publisher matches.
Action
Find Package by IDReturns one package from your PDQ library by its ID, including its latest version.
Action
List device softwareReturns the software installed on a PDQ Connect device, with name, publisher, version and install details.
Action
Set Device Custom Field ValueSets the value of a custom field on one PDQ device.
Action
Update custom fieldRenames an existing custom field definition in PDQ Connect.
Action
Update groupRenames a static device group and/or replaces its device membership.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from DNSFilter
DNSFilter to Enrich.soEnrich is a reverse email lookup tool that finds 50+ data points on your prospects using their email.
DNSFilter to OpenNEMAPI for Australian electricity market data, including real-time and historical generation, demand, and price...
DNSFilter to SupadataSupadata is a service for transcribing YouTube, TikTok, Twitter and Instagram video content, providing...
DNSFilter to TeamcampTeamcamp is an all-in-one project management application with project management, time tracking and invoicing
DNSFilter to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DNSFilter to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into PDQ Connect
HubSpot to PDQ ConnectHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PDQ ConnectGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PDQ ConnectGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PDQ ConnectGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PDQ ConnectGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PDQ ConnectMailchimp marketing automation and email platform.
Questions
DNSFilter and PDQ Connect, answered
What can start an automation from DNSFilter?
Any of DNSFilter's 4 triggers in the catalog, including Blocked Page Form Submitted, Policy Changed, Blocked Page Visited and Invoice Available. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PDQ Connect when something happens in DNSFilter?
Any of PDQ Connect's 17 actions, including Create Custom Field, Update custom field, Update group and Add group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PDQ Connect to DNSFilter?
Yes. When something happens in PDQ Connect, your agent can act in DNSFilter too. This page covers both directions: PDQ Connect's triggers and DNSFilter's actions are listed here as well.
Do I have to build a connector for DNSFilter or PDQ Connect?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use DNSFilter and PDQ Connect without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.