--- title: "Connect DNSFilter to Customer.io - APIANT.ai" description: "When \"Blocked Page Form Submitted\" fires in DNSFilter, your agent runs \"Send transactional email\" in Customer.io." canonical: "https://apiant.ai/connect/dnsfilter-to-customer-io" --- # Connect DNSFilter to Customer.io When **Blocked Page Form Submitted** fires in [DNSFilter](https://apiant.ai/connections/dnsfilter), your agent runs **Send transactional email** in [Customer.io](https://apiant.ai/connections/customer-io). Describe the whole flow and it is built, tested on every scenario and kept running. DNSFilter **4** triggers DNSFilter **29** actions Customer.io **10** 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 Customer.io 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 Customer.io - When **Blocked Page Form Submitted** in DNSFilter then **Send transactional email** in Customer.io - When **Policy Changed** in DNSFilter then **Create Anonymous Event** in Customer.io 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 Customer.io ## Triggers and actions 4 triggers · 39 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 **Create Anonymous Event** Records an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later. - Action **Create Event** Records an event for a person in Customer.io, which can trigger campaigns or update segments. - Action **Delete person** Deletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id. - Action **Get person** Look up a customer's attributes by customer_id. - Action **List segments** List all manual and data-driven segments in the workspace. - Action **Merge people** Merges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted. - Action **Remove people from segment** Removes people from a manual segment in Customer.io. Data-driven segments can't be changed this way. - Action **Send API-triggered broadcast** Trigger an API-triggered broadcast campaign to send immediately. - Action **Send transactional email** Send a one-off transactional email via a transactional message template. - Action **Suppress person** Deletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted. ## Each app on its own - [ **DNSFilter** DNSFilter is a cloud-based, AI-driven content filtering and threat protection service.](https://apiant.ai/connections/dnsfilter) - [ **Customer.io** With Customer.io you can send email, SMS, and push based on what people do or don't do in your app.](https://apiant.ai/connections/customer-io) 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 Customer.io - [ **HubSpot to Customer.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-customer-io) - [ **Wistia to Customer.io** Wistia makes it easy to host, track, and measure video engagement online.](https://apiant.ai/connect/wistia-to-customer-io) - [ **Salesforce to Customer.io** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-customer-io) - [ **Slack to Customer.io** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-customer-io) - [ **Google Sheets to Customer.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-customer-io) - [ **Gmail to Customer.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-customer-io) Questions ## DNSFilter and Customer.io, 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 Customer.io when something happens in DNSFilter? Any of Customer.io's 10 actions, including Create Anonymous Event, Create Event, Send API-triggered broadcast and Send transactional email. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Customer.io to DNSFilter? Customer.io has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Customer.io's API documentation and adds it. ### ### Do I have to build a connector for DNSFilter or Customer.io? 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 Customer.io 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.