InfraNestInfraNest
n8n
Automation

Connect infrastructure events to any n8n workflow — both ways

Send InfraNest events into n8n workflows, and let those workflows trigger actions back in InfraNest

InfraNest and n8n pass events and actions back and forth over a URL you set up once, in either direction.

  • Trigger workflows from your infrastructure. Certificate changes, expiries and weak or unexpected certificates, DNS record changes and mismatches, domain expiry, status and DNSSEC changes, dynamic IP changes, monitor alerts, server status changes, and the full lifecycle of watched domains (available, dropping, in auction, registered, released, renewed) can all start a workflow.
  • Act on InfraNest from n8n. Build a workflow that opens a maintenance window, pauses a monitor or resolves an incident in InfraNest — no console switch required.
  • Build against real data. Send a test event that imitates any of the above before you wire up the rest of the workflow.
  • See what moved. A delivery log shows what was sent and what arrived, in both directions.

What it looks like in InfraNest

Tell my own system when a monitor fails
ActivePausedSave automation

When this happens

Monitor alert

A monitor went down or recovered.

Change

Runs at 09:00 · Europe/Amsterdam · it’s 16:16 there now

Next runs:Tue 3 Nov, 09:00Wed 4 Nov, 09:00Thu 5 Nov, 09:00

This automation only runs when you click “Run now”.

Only if — optional filters

MatchAllAnyNoneof these conditions

Tip: a value can reference another field or the time using a placeholder.

Do this — actions run in order, stop at the first failure

1Call webhookPOST the event to an external URL.

In plain English

When Monitor alert if Status equals down, then Call webhook.

What you can do

Once n8n is connected, this is what InfraNest can do with it.

  • Events cover certificates, domains, DNS, monitors, servers and watched domains
  • Workflows can open maintenance windows, pause monitors or resolve incidents
  • Test event delivery before wiring up the rest of the workflow
  • Delivery log for both outbound and inbound traffic

How to connect it

  1. 1

    Get a webhook URL from n8n

    Add a Webhook node to a workflow in n8n and copy its Production URL, not the Test URL.

  2. 2

    Send InfraNest events to n8n

    In Integrations → n8n, select Add endpoint and paste the URL, then select Send test event to check it against a real payload.

  3. 3

    Let n8n trigger InfraNest back

    In Integrations → Custom webhook → URLs we give you, select Add incoming URL and use it in an HTTP Request node to open a maintenance window, pause a monitor or resolve an incident.

That’s it — n8n is connected.

Full setup guide

Set up with AI

I use n8n, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Webhook URL. Walk me through creating that in n8n: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.

Questions

#What events can start an n8n workflow?

Certificate changes and expiries, DNS record changes and mismatches, domain expiry and status changes, dynamic IP changes, monitor alerts, server status changes, and the stages a watched domain can move through, from going up for auction to being renewed.

#What can an n8n workflow do back in InfraNest?

A workflow can open a maintenance window, pause a monitor, or resolve an incident in InfraNest — triggered by posting to a URL InfraNest gives you.

#What happens if the webhook URL stops working or I rotate it?

If InfraNest can't reach your n8n URL, or your incoming URL is replaced, deliveries in that direction stop until you update it. The delivery log on the integration page shows the error so you can tell which side needs fixing.

#Can InfraNest change anything inside n8n itself?

No. InfraNest only sends events to the workflow URL you give it and receives calls from workflows you build — it doesn't create, edit or manage workflows inside n8n.

#What do I need before connecting n8n?

You need a Webhook node's Production URL from n8n, and if self-hosted it must be reachable from the internet — see the setup guide.

One dashboard for every provider

Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.

Free plan · No credit card required · Set up in minutes