Connect Make

Connect Make to InfraNest so infrastructure events can start a scenario, and so a scenario can trigger actions back in InfraNest — for anyone who wants monitor, domain, or certificate alerts to run automatically.

Overview

• Send InfraNest events (a monitor going down, a domain expiring, a certificate about to lapse) into a Make scenario.
• Let a Make scenario trigger InfraNest to open a maintenance window, pause a monitor, or resolve an incident.
• Both directions work by copying a web address between the two tools — there's nothing to install.

Before you start

1. In Make, add a Custom webhook module to a scenario.
2. Select Add to create the hook, then copy the address it shows — it looks like https://hook.eu2.make.com/abcdef123456.

NoteMake's editor lives on a region-specific address, so your webhook address may not match the example exactly.

Send InfraNest events to Make

1. Go to Integrations → Make.
2. Select Add endpoint and paste the webhook address.
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. Make's Determine data structure step is waiting for exactly this delivery — until one arrives, no fields are available to map.
5. Choose what gets sent: under Start an automation that posts to Make, pick a starting point like Send everything to my system, or build your own rule.

WarningAdding the endpoint doesn't send anything on its own — it only tells us where to send. An automation decides what gets sent, which is why step 5 matters. One rule can cover every event, or you can narrow it to the ones you care about.

Let Make 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 an HTTP module in your scenario, set to POST.
5. Back in InfraNest, use Start an automation Make can trigger and add what should happen — open a maintenance window, pause a monitor, resolve an incident.

Good to know

• The signing secret is shown once and never again. You can rotate it later; the old one stops working immediately.
• Your 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.
• Both directions keep a delivery log on the integration page, so you can see what went out and what arrived.
• You can add more than one endpoint — for example one scenario for incidents and another for domains.

Troubleshooting

Determine data structure never finishes. It's waiting for a real delivery. Select Send test event in InfraNest while the module is listening.

Nothing arrives in Make. Check that an automation actually posts to the endpoint — the endpoint alone is only a destination. The delivery log on the Make page shows whether we sent anything at all.

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