Connect Make

Connect Make to start a scenario when something changes in InfraNest, or let a scenario open a maintenance window, pause a monitor or resolve an incident — for anyone who wants their monitoring and their Make scenarios to react to each other automatically.

#Overview

• Start a Make scenario when a domain is expiring, a monitor goes down, or a certificate is about to lapse.
• Let a scenario in Make open a maintenance window, pause a monitor or resolve an incident in InfraNest.
• Both directions work by copying a web address between the two tools — nothing to install.

#Before you start

Get a webhook address from Make:

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 URL may not match the example exactly.

#Send InfraNest events to Make

1. Go to Integrations → Make and select Add endpoint. Before anything is set up it's on the Set up Make card; after that it's under Where events go on the Connections & settings tab.

2. Paste the webhook address 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. Make's Determine data structure step is waiting for exactly this — until one delivery arrives, no fields are available to map.

5. Choose what gets sent: under Automations that post here, the endpoint's page lists the Send everything to … 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 Make 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 Make 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 an HTTP module in your scenario, set to POST, with the body sent as 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 scenario sent is available in the rule as {{payload.your_field}}.

#Tips

• You can add more than one endpoint — for example one scenario for incidents and another for domains.
• What went out is listed under Recent deliveries, on the endpoint's page and on the Make page's Activity tab, with what Make 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.

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 leaks.

For what a delivery contains and how to check its signature, see Connect a custom webhook.

#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. 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 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. 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.

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.