Manage Make from InfraNest
Let your infrastructure and Make act on each other automatically
Connect InfraNest to Make in both directions, using a webhook address copied between the two tools.
- Trigger scenarios from your infrastructure: certificate changes, expirations and weak or unexpected certificates, DNS record changes, domain expiry and status changes, dynamic IP changes, monitor alerts, server status changes, and watched-domain events can all start a Make scenario.
- Act on InfraNest from a scenario: a Make scenario can open a maintenance window, pause a monitor, or resolve an incident, without you opening InfraNest to do it.
- Choose what gets sent: pick a starting rule like sending everything, or narrow it to only the events you care about.
- Verify what arrived: a signing secret lets you confirm deliveries really came from InfraNest, and a shared secret on the incoming side stops a leaked URL from triggering anything on its own.
NoteA delivery log on the integration page shows what was sent and what arrived, in both directions.
What you can do
- Outbound events: certificates, DNS, domains, monitors, servers
- Inbound triggers: maintenance windows, monitor pause, incident resolve
- Signing secret for outbound, shared secret for inbound
- Delivery log for both directions
How to connect it
- 1
Create a webhook in Make
Add a Custom webhook module to a scenario, select Add, and copy the address it shows.
- 2
Add the endpoint in InfraNest
Go to Integrations → Make, select Add endpoint, and paste the address. Save the signing secret shown.
- 3
Send a test event and pick what to send
Select Send test event so Make can read the data structure, then choose a starting rule under Start an automation that posts to Make.
- 4
Set up the reverse direction
Go to Integrations → Custom webhook → URLs we give you, select Add incoming URL, and use it in an HTTP module in your scenario. Add what it should do under Start an automation Make can trigger.
Questions
#What happens if the webhook URL or signing secret is compromised?
You can rotate the signing secret at any time; the old one stops working immediately. For the incoming direction, set a shared secret and regenerate the URL if it leaks, since anyone holding it can trigger your organization's automations.
#Can InfraNest change anything in Make, or only send events?
InfraNest only sends events to the URL you give it — it doesn't reach into Make itself. Make triggers actions back in InfraNest through its own scenario, using the incoming URL you set up.
#What can a Make scenario actually do in InfraNest?
It can open a maintenance window, pause a monitor, or resolve an incident. You define which of these happens under Start an automation Make can trigger.
#Why isn't anything arriving in Make after I added the endpoint?
Adding the endpoint only tells InfraNest where to send events — an automation still needs to be set to post to it. Check the delivery log on the integration page to see whether anything was sent at all.
#Do I need to build a custom rule to get started?
No, you can pick a starting rule like sending everything to your system, or narrow it down later to only the events you care about.
Often connected together
Start in seconds
Bring your whole infrastructure into one modern dashboard.
Free plan · No credit card required · Set up in minutes