--- title: "Connect incident.io to Nextdns - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add allowlist domain\" in Nextdns." canonical: "https://apiant.ai/connect/incident-io-to-nextdns" --- # Connect incident.io to Nextdns When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add allowlist domain** in [Nextdns](https://apiant.ai/connections/nextdns). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Nextdns **13** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and Nextdns to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What incident.io can start in Nextdns - When **New Incident** in incident.io then **Add allowlist domain** in Nextdns - When **New Incident** in incident.io 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 incident.io and Nextdns ## Triggers and actions 1 trigger · 23 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - Action **Add allowlist domain** Add a domain to a profile's allowlist. - Action **Add denylist domain** Adds a domain to a NextDNS profile's Denylist so DNS queries for it are blocked. - Action **Add profile** Creates a new NextDNS profile, optionally with its security, privacy, parental control, denylist, allowlist and settings configuration. - Action **Clear logs** Clears all DNS query logs for a NextDNS profile. - Action **Delete allowlist domain** Remove a domain from a profile's allowlist. - Action **Delete denylist domain** Removes a domain from a NextDNS profile's denylist. - Action **Delete profile** Deletes a NextDNS profile by its ID. - Action **Get profile** Retrieve a NextDNS profile by id. - Action **List allowlist domains** List domains on a profile's allowlist. - Action **List denylist domains** Lists the domains on a NextDNS profile's denylist. - Action **List profiles** Lists the profiles in the connected NextDNS account. - Action **Update performance settings** Update a profile's performance settings (ECS, cache boost, CNAME flattening). - Action **Update profile** Updates an existing NextDNS profile by ID. Only the sections you fill in are changed. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **Nextdns** Cloud-based DNS filtering service for blocking malware, ads, and trackers, with an API to manage profiles...](https://apiant.ai/connections/nextdns) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into Nextdns - [ **HubSpot to Nextdns** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-nextdns) - [ **Pushbullet to Nextdns** Pushbullet lets you send and receive pushes (notes, links, files) across your devices and to people, and...](https://apiant.ai/connect/pushbullet-to-nextdns) - [ **Telegram to Nextdns** Telegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.](https://apiant.ai/connect/telegram-to-nextdns) - [ **Salesforce to Nextdns** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-nextdns) - [ **Slack to Nextdns** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-nextdns) - [ **Google Sheets to Nextdns** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-nextdns) Questions ## incident.io and Nextdns, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Nextdns when something happens in incident.io? 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 incident.io? Nextdns has no triggers in the catalog today, so automations start in incident.io. 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 incident.io 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 incident.io 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.