Integration
Connect DNSFilter to MagicalAPI
When Blocked Page Form Submitted fires in DNSFilter, your agent runs Extract Resume Details in MagicalAPI. 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 MagicalAPI 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 MagicalAPI
When Blocked Page Form Submitted in DNSFilter
then Extract Resume Details in MagicalAPI
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 MagicalAPI
Triggers and actions 4 triggers · 12 actions
- Blocked Page Form Submitted
Triggers when a user submits the form on the blocked page.
- Blocked Page Visited
Triggered when someone in your DNSFilter account hits a blocked page.
- Invoice Available
Triggered when a new DNSFilter invoice becomes available.
- Policy Changed
Triggered when a DNSFilter policy is created or changed.
- Add to Allow List
Adds a single domain to a DNSFilter policy's allow list, with a note explaining why.
- Add to Block List
Adds a single domain to a DNSFilter policy's block list, with a note explaining why.
- Allow Category in a Policy
Allows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.
- Assign Policy to a Roaming Client
Assigns a DNSFilter policy to a roaming client, so that device filters against that policy.
- Assign Policy to a Site
Assigns a DNSFilter policy to a site, so traffic from that site filters against that policy.
- Block Category in a Policy
Blocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.
- Create Site
Creates a new site (network) in DNSFilter, optionally on a chosen policy and block page.
- Extract Resume Details
Parses a resume file into structured candidate details: contact info, summary, work history, education, certifications, skills, languages and interests.
- Get Company Data
Returns LinkedIn company details — size, industry, headquarters, funding, employees and recent posts — for a company looked up by name, LinkedIn username or website.
- Get Profile Data
Returns a LinkedIn person's profile data, including their experience, education and skills, looked up by their profile username.
- Review Resume and Provide Feedback
Reviews a resume and returns an overall score out of 100 with pros, cons and tips for each section, plus a suggested summary.
- Score Resume for Job
Scores how well a resume matches a job description and returns the match score with analysis.
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 MagicalAPI
Google Sheets to MagicalAPIGoogle Sheets
Gmail to MagicalAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MagicalAPIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
DNSFilter and MagicalAPI, 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 MagicalAPI when something happens in DNSFilter?
Any of MagicalAPI's 5 actions, including Extract Resume Details, Get Company Data, Get Profile Data and Review Resume and Provide Feedback. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from MagicalAPI to DNSFilter?
MagicalAPI has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads MagicalAPI's API documentation and adds it.
Do I have to build a connector for DNSFilter or MagicalAPI?
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.