Integration
Connect DNSFilter to Luma
When Blocked Page Form Submitted fires in DNSFilter, your agent runs Add ticket type in Luma. 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 Luma 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 Luma
When Blocked Page Form Submitted in DNSFilter
then Add ticket type in Luma
When Policy Changed in DNSFilter
then Add event in Luma
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 Luma
Triggers and actions 4 triggers · 48 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 eventAdds an existing event to your Luma calendar — either a Luma event you manage or an event hosted on another platform. The event is approved right away unless you choose to keep it pending for admin review.
Action
Add guestsAdds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.
Action
Add hostAdds a host to a Luma event, as a manager or as check-in staff, by email address.
Action
Add ticket typeCreates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.
Action
Apply contact tagApplies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
Action
Block contactBlocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.
Action
Cancel eventCancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
Action
Create Calendar PersonAdds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.
Action
Get calendarReturns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.
Action
Get eventReturns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
Action
Get guestReturns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.
Action
Import contactsImports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
Action
List contactsReturns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
Action
List eventsReturns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
Action
List guestsReturns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.
Action
List ticket typesReturns every ticket type set up for a Luma event, including its name, price and capacity.
Action
Send invitesSends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.
Action
Update eventUpdates an existing Luma event's details, such as its name, time, location, description, capacity, registration settings and page appearance. Fields left blank keep their current values.
Action
Update guest statusChanges a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.
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 Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LumaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LumaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LumaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LumaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LumaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
DNSFilter and Luma, 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 Luma when something happens in DNSFilter?
Any of Luma's 19 actions, including Create Calendar Person, Send invites, Update event and Update guest status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Luma to DNSFilter?
Luma has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.
Do I have to build a connector for DNSFilter or Luma?
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 Luma 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.