Skip to content

Connectors / Security and compliance · HTTP Connector

Automate DNSFilter with Tray.ai

Create a network, add domains to allow lists and create a user in DNSFilter.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with DNSFilter on Tray.ai?

DNSFilter is a DNS-based web filtering and threat protection service that blocks malicious and unwanted websites across networks and devices. Tray.ai connects to DNSFilter through the HTTP Connector, so your workflows can call the DNSFilter API alongside the rest of your stack.

  • Add domains to block lists when your security tool reports a new phishing domain.
  • Add domains to allow lists when IT approves a new business app in your service desk.
  • Create a network for each new office set up in your IT asset system.
  • Remove domains from block lists when the security team clears a false alarm.
Connects through
HTTP Connector
Authentication
An API key in a request header
Base URL
https://api.dnsfilter.com

Set it up

Connect DNSFilter to Tray.ai

Each step uses DNSFilter's own API details, from its documentation.

Step 1

Save DNSFilter's API key

Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://api.dnsfilter.com as the base URL. Or paste a cURL example from DNSFilter's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List networks”

It's one of 23 documented actions, under Networks. The response comes back as data the next step can map into your other apps.

Step 4

Hand it to an AI agent

Wrap “Create a network” and “Get a network” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.

What the DNSFilter API covers

6 resources and 23 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Networks

  • List networks
  • Create a network
  • Get a network
  • Update a network

Policies

  • Add domains to allow lists
  • Add domains to block lists
  • Remove domains from allow lists
  • Remove domains from block lists

Organizations

  • List organizations
  • Create an organization
  • Update an organization
  • Delete an organization

Organization users

  • List users
  • Create a user
  • Update a user
  • Delete a user

Block pages

  • List block pages
  • Create a block page
  • Update a block page
  • Delete a block page

Domains

  • Look up a domain
  • Bulk look up domains
  • Suggest a threat

Checked against DNSFilter's own documentation on 2026-10-22

api.dnsfilter.com/docs

Frequently asked questions

What can a Tray.ai workflow do in DNSFilter?

+

The DNSFilter API documents 23 actions across 6 resources (Networks, Policies, Organizations, Organization users, Block pages, Domains). For example: List networks; Add domains to allow lists; List organizations. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with DNSFilter?

+

The DNSFilter API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

See DNSFilter working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.