InfraNestInfraNest
Zapier
Automation

Connect infrastructure events to everything else you run

Send InfraNest events into any Zap, and trigger InfraNest actions from any Zap

InfraNest and Zapier exchange events in both directions, so your infrastructure and the rest of your stack stay in step without a person relaying the news.

  • Send infrastructure events out: certificate, domain, DNS, dynamic IP, monitor and server events reach Zapier, ready to start any Zap.
  • Cover expiry and health across your setup: certificates expiring or revoked, domains expiring or changing status, DNSSEC breaking, monitors alerting and servers changing status all flow out as they happen.
  • Track watched domains: a domain you're watching becoming available, going to auction, being released or renewed can all kick off a Zap.
  • Trigger InfraNest from anywhere: a Zap can open a maintenance window, pause a monitor, or resolve an incident in InfraNest, so other tools can act back on your infrastructure.

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 Zapier is connected, this is what InfraNest can do with it.

  • Certificate, domain, DNS and dynamic IP events sent out
  • Monitor and server status events sent out
  • Watched-domain events (available, auction, released, renewed)
  • Zap-triggered maintenance windows, monitor pauses and incident resolution

How to connect it

  1. 1

    Get a Catch Hook URL from Zapier

    Create a Zap, choose the "Webhooks by Zapier" trigger and the "Catch Hook" event, then copy the URL it shows you.

  2. 2

    Send InfraNest events to Zapier

    Paste the URL into Integrations → Zapier under Add endpoint, then select Send test event so Zapier has something to map fields from.

  3. 3

    Let Zapier trigger InfraNest back

    Add an incoming URL under Integrations → Custom webhook → URLs we give you, paste it into a Webhooks by Zapier action, and set what it should do under Start an automation Zapier can trigger.

That’s it — Zapier is connected.

Full setup guide

Set 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 I send to Zapier?

Certificate changes and expiry, domain expiry and status changes, DNS record changes, DNSSEC problems, dynamic IP changes, monitor alerts, server status changes, and watched-domain events like becoming available or going to auction. You can narrow an endpoint to only the events you care about, or send everything from the start.

#What can a Zap do back in InfraNest?

A Zap can open a maintenance window, pause a monitor, or resolve an incident — each one set up as its own automation triggered by an incoming URL you give to Zapier.

#What happens if the Catch Hook URL or incoming URL stops working?

If a Zap is deleted or a URL is regenerated, deliveries to or from it stop immediately — check the Activity tab on the integration page to see what went out and what arrived, then update the URL on whichever side changed.

#Can InfraNest verify that events really came from Zapier, or vice versa?

You can set a signing secret on outbound events and a shared secret on your incoming URL, so a leaked URL on its own isn't enough to trigger anything.

#What do I need before connecting Zapier?

You need a Zapier account to create the Catch Hook URL and, if triggering InfraNest back, an incoming URL set up on your side — 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