Connect InfraNest to anything that speaks HTTP
Send InfraNest events anywhere, or let any tool trigger an automation here — no built-in integration required
Custom webhook is a two-way door between InfraNest and whatever else you run — no waiting on a purpose-built integration.
- Send events out: certificate problems, DNS changes, domain status and expiry, dynamic IP changes, server status changes and monitor alerts all go to a URL you supply, so your own system hears about them without you checking InfraNest for them.
- Trigger InfraNest from anywhere: InfraNest gives you a URL of its own. Point any tool that can make a web request at it, and it can start one of your automations — open a maintenance window, pause a monitor, resolve an incident — even if that tool has no integration with InfraNest at all.
- Pick what goes out: send everything by default, or narrow an endpoint down to the specific events you want.
- Verify what you receive: each delivery is signed, so your receiver can confirm it really came from InfraNest before acting on it.
What it looks like in InfraNest
When this happens
Monitor alert
A monitor went down or recovered.
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
In plain English
When Monitor alert if Status equals down, then Call webhook.
Choose a trigger and an action to see a live summary.
What you can do
Once Webhook is connected, this is what InfraNest can do with it.
- Outbound events for certificates, DNS, domains, dynamic IPs, servers and monitors
- An InfraNest-generated URL that any tool can call to start an automation
- Signed deliveries you can verify before trusting them
- Independent inbound and outbound setup — use either, or both
Not supported
This integration only moves events in and out — it doesn't read or manage your servers, DNS or domains. Those stay with InfraNest's own provider integrations.
How to connect it
- 1
Add an endpoint to send events out
Get InfraNest posting to your own system by pasting its URL under Integrations → Custom webhook → Add endpoint.
- 2
Save the signing secret
Get a way to verify deliveries are genuine by copying the secret shown once after saving, and giving it to your receiver.
- 3
Add an incoming URL to trigger InfraNest
Get a URL any tool can call by going to Integrations → Custom webhook → URLs we give you → Add incoming URL, then use it to start an automation.
That’s it — Webhook is connected.
Full setup guideSet up with AI
I use Webhook, 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 Webhook: 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 exactly can trigger an automation here?
Anything able to send an HTTP POST to the incoming URL InfraNest generates for you — including tools InfraNest has no built-in integration with. You decide what that triggers when you build the automation.
#What happens if my signing secret or incoming URL leaks?
Rotate the signing secret and the old one stops working immediately — update your receiver with the new one. For an incoming URL, use Regenerate URL for the same effect, or set a shared secret so a leaked URL alone isn't enough to trigger anything.
#Can InfraNest change anything on the other system's side?
No. This integration only sends and receives events — it doesn't read or manage anything on the receiving system. What happens with an event once it arrives is entirely up to the system you built.
#Do I have to use both directions?
No. Sending events out and accepting incoming triggers are set up separately, so you can use just one or both, depending on what you need.
#What do I need before connecting Custom webhook?
Just a URL your service accepts POST requests on, or a plan to point another tool at the URL InfraNest gives you — no API key required; see the setup guide.
Often connected together
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