Connect InfraNest events to any Make scenario, both ways
Send infrastructure events into Make, and let Make scenarios trigger actions back in InfraNest
You connect InfraNest and Make with a webhook address copied between the two, and events start flowing in both directions.
- Send events out: certificate changes, expiry and weak or unexpected certificates, DNS record changes and live mismatches, domain expiry and DNSSEC problems, dynamic IP changes, monitor alerts, server status changes, and watched-domain activity (available, registered, released, renewed, in auction, dropping soon, funding short, failed) all reach your scenario.
- Choose what gets sent: start with everything, or narrow the automation to only the events you care about.
- Trigger InfraNest from Make: a scenario can open a maintenance window, pause a monitor, or resolve an incident, by posting to a URL InfraNest gives you.
- Run more than one endpoint: point one scenario at incidents and another at domain events, for example.
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 Make is connected, this is what InfraNest can do with it.
- Events cover certificates, domains, DNS, monitors, servers, dynamic IPs
- Scenarios can open maintenance windows, pause monitors, resolve incidents
- Multiple endpoints for different scenarios
- Delivery log shows what was sent and what arrived
How to connect it
- 1
Create a webhook in Make
Gets you the address InfraNest will send events to — add a Custom webhook module to a scenario and select Add to create and copy it.
- 2
Add the endpoint in InfraNest
Starts events flowing — go to Integrations → Make, paste the address, and select Send test event so Make can determine the data structure.
- 3
Set up the return path (optional)
Lets a scenario trigger InfraNest back — go to Integrations → Custom webhook → URLs we give you, select Add incoming URL, and post to it from an HTTP module.
That’s it — Make is connected.
Full setup guideSet up with AI
I use Make, 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 Make: 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
#Why isn't Make picking up any fields from the event?
Make's Determine data structure step needs one real delivery before it can map anything. Select Send test event in InfraNest while that module is listening, and it will complete.
#What happens if I lose or leak the incoming URL?
The incoming URL works like a password — anyone with it can trigger your automations, so set a shared secret when you create it. If it leaks, you can regenerate the URL and the old one stops working immediately.
#What does InfraNest change on Make's side?
Nothing — InfraNest only sends events to the webhook address you give it and listens on the incoming URL you create. Everything else, including what the scenario does with that data, stays inside Make.
#Can I send only some events, not everything?
Yes. The endpoint starts with everything sent by default, but you can narrow the automation behind it to just the events a given scenario needs.
#What do I need before connecting Make?
You need a webhook address from a Make scenario (add a Custom webhook module, then Add) — 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