Connect Zapier

Connect Zapier to InfraNest so the two tools can trigger each other — no coding or installing required, just a couple of URLs copied between them. This is for anyone who wants InfraNest events to start 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 else 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 and select Add endpoint. Before anything is set up it's on the Set up Zapier card; after that it's under Where events go on the Connections & settings tab.

2. Paste the Catch Hook URL into Endpoint URL. Leave Send every event here ticked, so every event is sent from the start, and select Create.

3. Copy the signing secret shown once after saving, if you want to verify that deliveries really came from us.

4. On the endpoint's page, pick an event in the list next to Send test event, then select Send test event. Zapier can't map any fields until it has received something, so do this before continuing in Zapier.

5. Choose what gets sent: under Automations that post here, the endpoint's 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 Or start from a ready-made automation: or build your own rule.

#Let Zapier trigger InfraNest

1. Go to Integrations → Custom webhook and select Add incoming URL (under URLs we give you on the Connections & settings tab, once anything is set up there). Incoming URLs belong to no single tool, so they live there: on the Zapier page, Open incoming URLs takes you to them.
2. Give it a Name you'll recognise later — you pick it by name when writing the rule.
3. Optionally set a Shared secret (optional), 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, with the POST event and Payload Type set to json. If you set a secret, add it as the X-InfraNest-Secret header.
5. Back in InfraNest, start an automation from Let another tool trigger an automation (or with the Incoming webhook trigger) and add what should happen — open a maintenance window, pause a monitor, resolve an incident. What the Zap sent is available in the rule as {{payload.your_field}}.

WarningYour incoming URL works like a password. Anyone holding it can trigger your workspace's automations, so set a shared secret and use Regenerate URL if it ever leaks.

#Good to know

• The signing secret is shown once and never again. Rotate signing secret on the endpoint's page gives you a new one; the old one stops working immediately.
• What went out is listed under Recent deliveries, on the endpoint's page and on the Zapier page's Activity tab, with what Zapier answered. A failed delivery has a Retry button.
• What came in is listed under What has arrived on the incoming URL's page, including calls we turned away and why.
• You can add more than one endpoint — for example one Zap for incidents and another for domains.
• For what a delivery contains and how to check its signature, see Connect a custom webhook.

#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. Then open the incoming URL's page: What has arrived lists every call, and a call we turned away says why. Send the body as JSON — anything else arrives empty.

TipSet up the test event in InfraNest before you touch Zapier's mapping step — it saves a round trip since Zapier can't suggest fields until it has seen a real delivery.