Let infrastructure events start Zaps, and Zaps trigger InfraNest back
Connect InfraNest to automate actions based on certificate, domain, monitor and server events
Connect InfraNest to Zapier and stop treating infrastructure events as something you have to notice yourself.
- Send events out: certificate changes, expiring or revoked certificates, DNS record changes, domain expiry and status changes, dynamic IP changes, monitor alerts, server status changes and watched-domain updates can all start a Zap.
- Choose what triggers a Zap: send everything, or build a rule that narrows it to the events you care about.
- Trigger InfraNest from Zapier: a Zap can open a maintenance window, pause a monitor or resolve an incident, so response steps run without you opening InfraNest.
- Confirm delivery: a log on the integration page shows what was sent and what arrived, so a silent failure doesn't go unnoticed.
NoteAdding an endpoint only tells InfraNest where to send events — an automation rule decides what actually gets sent.
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 15:49 there now
Next runs:Sat 19 Sept, 09:00Sun 20 Sept, 09:00Mon 21 Sept, 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.
What you can do
Once Zapier is connected, this is what InfraNest can do with it.
- 15 event types can start a Zap
- Rule-based filtering of which events post out
- Incoming URL lets Zaps trigger InfraNest actions
- Shared secret and signing secret for verification
- Delivery log for both directions
How to connect it
- 1
Get a Catch Hook URL from Zapier
Create a Zap with the Webhooks by Zapier trigger and Catch Hook event, then copy the URL Zapier shows you.
- 2
Add the endpoint in InfraNest
Go to Integrations → Zapier, select Add endpoint, and paste the Catch Hook URL. Copy the signing secret shown once if you want to verify deliveries.
- 3
Send a test event and set your rule
Select Send test event and pick an event to imitate, then under Start an automation that posts to Zapier choose Send everything to my system or build your own rule.
- 4
Set up the reverse direction if you need it
Go to Integrations → Custom webhook → URLs we give you, select Add incoming URL, and use Start an automation Zapier can trigger to define what a Zap can do in InfraNest.
That’s it — Zapier is connected.
Full setup guideSet up with AI
I use Zapier, 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 Zapier: 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 trigger a Zap?
Certificate changes, expiry, revocation and weak-certificate alerts, DNS record changes, domain expiry and status changes, dynamic IP changes, monitor alerts, server status changes and watched-domain updates can all start a Zap.
#Can Zapier make changes in InfraNest, or just receive events?
Both. You can also give InfraNest a URL from a Webhooks by Zapier action, then set up an automation in InfraNest so that Zap can open a maintenance window, pause a monitor or resolve an incident.
#What happens if the Catch Hook URL or signing secret is revoked or lost?
The signing secret is shown once and never again, but you can rotate it — the old one stops working immediately. If your Zapier endpoint changes, add a new endpoint in InfraNest with the new Catch Hook URL.
#Is it safe if someone gets hold of my incoming URL?
Treat it like a password — anyone with it can trigger your automations. Set a shared secret when you create it, and regenerate the URL if it ever leaks.
#Why isn't anything showing up in Zapier after I connect?
Adding an endpoint only tells InfraNest where to send events; an automation rule has to actually post to it. Check the delivery log on the Zapier integration page to see whether anything was sent at all.
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