Integration
Connect Gridfox to Nextdns
When Record Created fires in Gridfox, your agent runs Add allowlist domain in Nextdns. 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 Gridfox and Nextdns 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 Gridfox can start in Nextdns
When Record Created in Gridfox
then Add allowlist domain in Nextdns
When Record Created or Updated in Gridfox
then Add denylist domain in Nextdns
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 Gridfox and Nextdns
Triggers and actions 2 triggers ยท 22 actions
Trigger
Record CreatedTriggers when a new record is created.
Trigger
Record Created or UpdatedFires when a record in the chosen Gridfox table is created or updated.
Action
Add recordCreate a record in a table.
Action
Add userAdd a user to the project.
Action
Delete recordDelete a record.
Action
Find recordsSearch records in a table by search parameters.
Action
Get recordGet a record by reference field value.
Action
Get record auditGet audit history for a record.
Action
List tablesList tables in the project.
Action
List User Groupslists the project's user groups with their member users (id, email).
Action
Update recordUpdate a record by reference field value.
Action
Add allowlist domainAdd a domain to a profile's allowlist.
Action
Add denylist domainAdds a domain to a NextDNS profile's Denylist so DNS queries for it are blocked.
Action
Add profileCreates a new NextDNS profile, optionally with its security, privacy, parental control, denylist, allowlist and settings configuration.
Action
Clear logsClears all DNS query logs for a NextDNS profile.
Action
Delete allowlist domainRemove a domain from a profile's allowlist.
Action
Delete denylist domainRemoves a domain from a NextDNS profile's denylist.
Action
Delete profileDeletes a NextDNS profile by its ID.
Action
Get profileRetrieve a NextDNS profile by id.
Action
List allowlist domainsList domains on a profile's allowlist.
Action
List denylist domainsLists the domains on a NextDNS profile's denylist.
Action
List profilesLists the profiles in the connected NextDNS account.
Action
Update performance settingsUpdate a profile's performance settings (ECS, cache boost, CNAME flattening).
Action
Update profileUpdates an existing NextDNS profile by ID. Only the sections you fill in are changed.
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 Gridfox
Gridfox to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Gridfox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gridfox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gridfox to MailchimpMailchimp marketing automation and email platform.
Gridfox to StripeStripe is a payment processing platform for online businesses.
Gridfox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Nextdns
Pushbullet to NextdnsPushbullet lets you send and receive pushes (notes, links, files) across your devices and to people, and...
Telegram to NextdnsTelegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.
HubSpot to NextdnsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NextdnsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NextdnsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NextdnsGoogle Sheets
Questions
Gridfox and Nextdns, answered
What can start an automation from Gridfox?
Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Nextdns when something happens in Gridfox?
Any of Nextdns's 13 actions, including Update performance settings, Update profile, Add allowlist domain and Add denylist domain. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Nextdns to Gridfox?
Nextdns has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads Nextdns's API documentation and adds it.
Do I have to build a connector for Gridfox or Nextdns?
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 Gridfox and Nextdns 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.