Manage n8n from InfraNest
Let infrastructure events start n8n workflows, and n8n trigger InfraNest back
Connect n8n in both directions: send infrastructure events out to trigger workflows, and let workflows act back on InfraNest.
- Trigger workflows from real events — certificate changes, expiry and revocation, DNS record changes, domain expiry and status changes, dynamic IP changes, monitor alerts, server status changes, and watched-domain results can all start an n8n workflow, so you stop manually checking for them.
- Choose what gets sent — send everything to one workflow, or build a rule that narrows it down to the events you actually act on.
- Let n8n act on InfraNest — a workflow can open a maintenance window, pause a monitor, or resolve an incident, so routine responses don't wait on someone opening InfraNest.
- Verify what you receive and send — a signing secret confirms events came from InfraNest, and a shared secret on your incoming URL stops it from being triggered by anyone who finds the address.
NoteAdding an endpoint only tells InfraNest where to deliver — you still need to set up the automation that decides what gets sent.
What you can do
- Outbound events for certificates, DNS, domains, monitors and servers
- Inbound URL n8n can call to trigger InfraNest actions
- Signing secret to verify deliveries
- Shared secret to protect your incoming URL
- Delivery log for both directions
How to connect it
- 1
Get a Production URL from n8n
Add a Webhook node to your workflow and copy its Production URL — the Test URL only listens while the editor is open.
- 2
Add the endpoint in InfraNest
Go to Integrations → n8n, select Add endpoint, and paste the Production URL. Copy the signing secret shown once after saving.
- 3
Send a test event and choose what to send
Select Send test event to try it against a real payload, then under Start an automation that posts to n8n pick a starting point like Send everything to my system or build your own rule.
- 4
Optionally let n8n trigger InfraNest back
Go to Integrations → Custom webhook → URLs we give you, select Add incoming URL, and use Start an automation n8n can trigger to define what it should do.
Questions
#What happens if I lose the signing secret or it leaks?
The signing secret is shown once and never shown again, but you can rotate it. The old one stops working immediately once you do.
#What can n8n actually do inside InfraNest?
A workflow calling your incoming URL can open a maintenance window, pause a monitor, or resolve an incident. It can't do anything beyond what you set up under Start an automation n8n can trigger.
#My incoming URL leaked — what's at risk?
Your incoming URL works like a password: anyone holding it can trigger your organization's automations. Set a shared secret when creating it, and regenerate the URL if you think it's been exposed.
#Why isn't anything arriving from InfraNest?
The most common cause is using the Test URL instead of the node's Production URL — the test one only listens while the n8n editor is open. If you self-host n8n, also check that the address is reachable from the internet and not behind a VPN or local firewall rule.
#Can I send different events to different workflows?
Yes, you can add more than one endpoint — for example one workflow for incidents and another for domain events — and control what each receives with its own automation rule.
Often connected together
Start in seconds
Bring your whole infrastructure into one modern dashboard.
Free plan · No credit card required · Set up in minutes