Integration
Connect DNSFilter to Dreamdata
When something happens in DNSFilter, your agent does the next thing in Dreamdata. Describe it 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 Dreamdata to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Dreamdata
When Blocked Page Form Submitted in DNSFilter
then Track Page View in Dreamdata
When Policy Changed in DNSFilter
then Group User in Dreamdata
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 Dreamdata
Triggers and actions 4 triggers · 12 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 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 SiteCreates a new site (network) in DNSFilter, optionally on a chosen policy and block page.
Action
Group UserAssociates a user with different properties, such as company name and size.
Action
Identify UserIdentifies user by traits.
Action
Track and IdentifyTracks an event and identifies the user.
Action
Track EventTracks a custom event.
Action
Track Page ViewSends a "page" message to Dreamdata's batch ingestion endpoint to record a page view. Fields: userId or anonymousId (required, one of), category (optional), name (optional), properties (optional dict — url, title, referrer, etc.), context, timestamp. Distinct from the existing Track Event op — "page" is its own message type alongside identify/track/group/alias per Dreamdata's tracking API spec.
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 SupadataSupadata is a service for transcribing YouTube, TikTok, Twitter and Instagram video content, providing...
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...
DNSFilter to Google SheetsGoogle Sheets
DNSFilter to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Dreamdata
HubSpot to DreamdataHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DreamdataSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DreamdataSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DreamdataGoogle Sheets
Gmail to DreamdataGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DreamdataGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
DNSFilter and Dreamdata, 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 Dreamdata when something happens in DNSFilter?
Any of Dreamdata's 5 actions, including Group User, Identify User, Track and Identify and Track Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Dreamdata to DNSFilter?
Dreamdata has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Dreamdata's API documentation and adds it.
Do I have to build a connector for DNSFilter or Dreamdata?
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.
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.