Connect Zapier

Connect Zapier to link InfraNest with thousands of other apps — no coding needed. This is for anyone who wants InfraNest events to kick off a Zap, or a Zap to trigger an action in InfraNest.

Overview

• Start a Zap when a domain is expiring, a monitor goes down, or a certificate is about to lapse.
• Let a Zap open a maintenance window, pause a monitor, or resolve an incident in InfraNest.
• Both directions work by copying a URL between InfraNest and Zapier — nothing to install.

Before you start

Get a Catch Hook URL from Zapier:

1. In Zapier, create a Zap and choose the Webhooks by Zapier trigger.
2. Choose the Catch Hook event.
3. Copy the URL Zapier shows — it looks like https://hooks.zapier.com/hooks/catch/123456/abcdef.

Send InfraNest events to Zapier

1. Go to Integrations → Zapier.
2. Select Add endpoint and paste the Catch Hook URL. Leave Send every event here ticked, so every event is sent from the start.
3. Copy the signing secret shown once after saving, if you want to verify that deliveries really came from us.
4. Select Send test event and pick the event it should imitate. Zapier can't map any fields until it has received something, so do this before continuing in Zapier.
5. Choose what gets sent: the endpoint page lists the automation it started. Open it to narrow it to the events you care about — or, if you unticked the box, pick a starting point under Start an automation that posts to Zapier or build your own rule.

Let Zapier trigger InfraNest

1. Go to Integrations → Custom webhook → URLs we give you and select Add incoming URL.
2. Give it a name you'll recognise later — you pick it by name when writing the rule.
3. Optionally set a shared secret, so a leaked URL on its own isn't enough to trigger anything.

4. Copy Your URL into a Webhooks by Zapier action in your Zap, set to POST.
5. Back in InfraNest, use Start an automation Zapier can trigger and add what should happen — open a maintenance window, pause a monitor, resolve an incident.

Tips

TipYou can add more than one endpoint — for example one Zap for incidents and another for domains.

• Both directions keep a delivery log under the integration page's Activity tab, so you can see what went out and what arrived.

WarningYour incoming URL works like a password. Anyone holding it can trigger your organization's automations, so set a shared secret and regenerate the URL if it leaks. The signing secret is shown once and never again — you can rotate it later, but the old one stops working immediately.

Troubleshooting

Zapier shows no fields to map. Its Catch Hook only learns the structure once it has actually received something. Select Send test event in InfraNest, then continue setting up the Zap.

Nothing arrives in Zapier. If you unticked Send every event here, check that an automation posts to the endpoint — the endpoint alone is only a destination. The delivery log on the Zapier page shows whether we sent anything at all.

Your Zap doesn't trigger InfraNest. Confirm the Zap posts to the exact incoming URL, and that the shared secret — if you set one — is sent as the X-InfraNest-Secret header.