Integration
Connect DNSFilter to Flodesk
When Blocked Page Form Submitted fires in DNSFilter, your agent runs Find a Subscriber by Email Address in Flodesk. 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 Flodesk 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)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 can start in Flodesk
When Blocked Page Form Submitted in DNSFilter
then Find a Subscriber by Email Address in Flodesk
When Policy Changed in DNSFilter
then Add custom field in Flodesk
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 Flodesk
Triggers and actions 4 triggers · 44 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
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.
Action
Add custom fieldCreates a new subscriber custom field in your Flodesk account with the label you choose.
Action
Add Existing Subscriber to SegmentAdds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.
Action
Add Existing Subscriber to WorkflowAdds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.
Action
Add segmentCreates a new segment in your Flodesk account and returns it.
Action
Create/Update SubscriberCreates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.
Action
Find a Subscriber by Email AddressLooks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.
Action
Get segmentReturns a single Flodesk segment, including its name, color, type and number of active subscribers.
Action
List campaignsReturns the email campaigns in your Flodesk account, optionally filtered by status or a search term.
Action
List custom fieldsReturns every subscriber custom field defined in your Flodesk account, with each field's key and display label.
Action
List segmentsReturns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.
Action
List subscribersReturns subscribers in your Flodesk account, optionally filtered by status or segment.
Action
List workflowsReturns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).
Action
Remove Existing Subscriber From SegmentRemoves an existing Flodesk subscriber from one or more segments and returns the updated subscriber.
Action
Remove Existing Subscriber From WorkflowRemoves an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.
Action
Unsubscribe SubscriberUnsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.
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 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.
DNSFilter to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Flodesk
EasyCSV to FlodeskEasyCSV enables your users or team members to import CSV files and Google Sheets into your app or any public...
HubSpot to FlodeskHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FlodeskSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FlodeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FlodeskGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to FlodeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
DNSFilter and Flodesk, 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 Flodesk when something happens in DNSFilter?
Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Flodesk to DNSFilter?
Flodesk has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Flodesk's API documentation and adds it.
Do I have to build a connector for DNSFilter or Flodesk?
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 Flodesk 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.