---
title: "Connect DNSFilter to Okta - APIANT.ai"
description: "When \"Blocked Page Form Submitted\" fires in DNSFilter, your agent runs \"Add User to Group\" in Okta."
canonical: "https://apiant.ai/connect/dnsfilter-to-okta"
---

# Connect DNSFilter to Okta

When **Blocked Page Form Submitted** fires in [DNSFilter](https://apiant.ai/connections/dnsfilter), your agent runs **Add User to Group** in [Okta](https://apiant.ai/connections/okta). Describe the whole flow and it is built, tested on every scenario and kept running.

DNSFilter **4** triggers DNSFilter **29** actions Okta **22** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want DNSFilter and Okta to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What DNSFilter can start in Okta

- When **Blocked Page Form Submitted** in DNSFilter then **Add User to Group** in Okta
- When **Policy Changed** in DNSFilter then **Create User** in Okta

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 Okta

## Triggers and actions 4 triggers · 51 actions

- Trigger

**Blocked Page Form Submitted**

Triggers when a user submits the form on the blocked page.

- Trigger

**Blocked Page Visited**

Triggered when someone in your DNSFilter account hits a blocked page.

- Trigger

**Invoice Available**

Triggered when a new DNSFilter invoice becomes available.

- Trigger

**Policy Changed**

Triggered when a DNSFilter policy is created or changed.

- Action

**Add IP address**

Adds an IP address to a DNSFilter site (network) so DNS traffic from that address is filtered under the site's policy.

- Action

**Add organization user**

Adds a new or existing user, by email, to a DNSFilter organization with the chosen role.

- Action

**Add policy**

Creates a new DNS filtering policy in a DNSFilter organization, with its allow/block lists, blocked categories and safe-search settings.

- Action

**Add scheduled report**

Creates a scheduled report that emails DNSFilter traffic and threat summaries for an organization on a recurring schedule.

- Action

**Add to Allow List**

Adds a single domain to a DNSFilter policy's allow list, with a note explaining why.

- Action

**Add to Block List**

Adds a single domain to a DNSFilter policy's block list, with a note explaining why.

- Action

**Allow Category in a Policy**

Allows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.

- Action

**Assign Policy to a Roaming Client**

Assigns a DNSFilter policy to a roaming client, so that device filters against that policy.

- Action

**Assign Policy to a Site**

Assigns a DNSFilter policy to a site, so traffic from that site filters against that policy.

- Action

**Block Category in a Policy**

Blocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.

- Action

**Create Organization**

Creates a new organization under an MSP in DNSFilter.

- Action

**Create Site**

Creates a new site (network) in DNSFilter, optionally on a chosen policy and block page.

- Action

**Delete IP address**

Removes an IP address from your DNSFilter account.

- Action

**Delete organization user**

Removes a user from a DNSFilter organization. The user's account itself is not deleted.

- Action

**Delete policy**

Deletes a policy from your DNSFilter account.

- Action

**Delete site**

Deletes a site (network) from DNSFilter. A site with active roaming clients or LAN proxies cannot be deleted.

- Action

**Find domain by FQDN**

Returns the domain DNSFilter has on record for a fully qualified domain name, including its host, name and associated categories and applications.

- Action

**Get organization**

Returns 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 policy**

Returns 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 site**

Returns a DNSFilter site (network) by its ID, including its name, address, block page settings and linked policies.

- Action

**List categories**

Returns every DNSFilter content category, including internal categories, with each category's name, description and whether it is a security threat.

- Action

**List IP addresses**

Returns the IP addresses associated with your DNSFilter account, optionally narrowed by a search term.

- Action

**List organizations**

Returns all organizations your DNSFilter account can access, optionally filtered by name, type or MSP.

- Action

**List organization users**

Returns the users of a DNSFilter organization, with their contact details, role and organization access.

- Action

**List policies**

Returns every DNS filtering policy your DNSFilter account can access, with each policy's allow list, block list and settings.

- Action

**List sites**

Returns the sites (networks) in your DNSFilter account, optionally filtered by a search term or by whether a policy is assigned.

- Action

**Update organization**

Updates an organization's name, billing contact, address, plan and privacy settings, and returns the updated organization.

- Action

**Update policy**

Updates a DNSFilter policy's name, safe-search settings, allow/block lists, blocked categories, countries and applications.

- Action

**Update site**

Updates a site's name, organization, policies, block page, address, IP addresses and local DNS settings, and returns the updated site.

- Action

**Activate User**

Activates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off.

- Action

**Add group**

Creates a new Okta-managed group with a name, an optional description, and any custom group profile attributes defined in your org.

- Action

**Add User to Group**

Adds an existing Okta user to an Okta-managed group.

- Action

**Assign user to application**

Assigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user.

- Action

**Create User**

Creates a new user in your Okta org, with or without credentials, and returns the new user's id and status.

- Action

**Deactivate User**

Deactivates an Okta user, deprovisioning them from all assigned apps. This cannot be undone by the deactivation itself and may destroy the user's data in those apps.

- Action

**Delete group**

Permanently deletes a group from your Okta org by its ID.

- Action

**Delete user**

Permanently deletes a deactivated Okta user. If the user is still active, this deactivates them instead, and running it a second time deletes them.

- Action

**Find Group by Name**

Returns the Okta groups whose name matches the name you specify, either exactly or by a partial match.

- Action

**Find User by Email**

Returns the Okta users whose primary email matches the email you specify, including deprovisioned users.

- Action

**Get group**

Returns one Okta group by its id, including its profile name, description and any custom attributes.

- Action

**Get user**

Returns one Okta user, including their status, timestamps, credentials summary, and standard and custom profile attributes. An error occurs if the user is not found.

- Action

**List applications**

Returns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression.

- Action

**List group members**

Returns the users who are members of an Okta group, with their profiles, including any custom attributes. Results can be narrowed with a search expression.

- Action

**List groups**

Returns the groups in your Okta organization, optionally narrowed by a search, filter or name match.

- Action

**List users**

Returns the users in your Okta organization, optionally narrowed by a search, filter or name query.

- Action

**Remove User From Group**

Removes a user from a group managed directly in Okta. The user account itself is not changed.

- Action

**Reset user password**

Starts a password reset for an Okta user and either emails them the reset link or returns the link. The user moves to Recovery status and can't sign in until they finish the reset.

- Action

**Suspend User**

Suspends an active Okta user so they can't sign in, while keeping their group and app assignments. Suspended users can later be unsuspended or deactivated.

- Action

**Unsuspend user**

Unsuspends a suspended Okta user and returns them to the Active state.

- Action

**Update group**

Updates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value.

- Action

**Update user**

Updates an existing Okta user's profile, including custom profile attributes, or credentials. Fields left blank keep their current values.

## Each app on its own

- [ **DNSFilter** DNSFilter is a cloud-based, AI-driven content filtering and threat protection service.](https://apiant.ai/connections/dnsfilter)
- [ **Okta** Okta helps companies manage and secure user authentication into modern applications, and for developers to...](https://apiant.ai/connections/okta)

Reviews

## What our customers say

## More from DNSFilter

- [ **DNSFilter to Enrich.so** Enrich is a reverse email lookup tool that finds 50+ data points on your prospects using their email.](https://apiant.ai/connect/dnsfilter-to-enrich-so)
- [ **DNSFilter to Supadata** Supadata is a service for transcribing YouTube, TikTok, Twitter and Instagram video content, providing...](https://apiant.ai/connect/dnsfilter-to-supadata)
- [ **DNSFilter to Teamcamp** Teamcamp is an all-in-one project management application with project management, time tracking and invoicing](https://apiant.ai/connect/dnsfilter-to-teamcamp)
- [ **DNSFilter to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/dnsfilter-to-hubspot)
- [ **DNSFilter to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/dnsfilter-to-salesforce)
- [ **DNSFilter to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/dnsfilter-to-slack)

## More into Okta

- [ **HubSpot to Okta** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-okta)
- [ **Salesforce to Okta** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-okta)
- [ **Slack to Okta** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-okta)
- [ **Google Sheets to Okta** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-okta)
- [ **Gmail to Okta** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-okta)
- [ **Google Calendar to Okta** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-okta)

Questions

## DNSFilter and Okta, 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 Okta when something happens in DNSFilter?

Any of Okta's 22 actions, including Create User, Update group, Update user and Activate User. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Okta to DNSFilter?

Okta has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Okta's API documentation and adds it.

###

### Do I have to build a connector for DNSFilter or Okta?

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 Okta 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.
