Schedule Maintenance Windows via Webhook: Zabbix, Nagios & Kuma

Schedule Maintenance Windows Across Zabbix, Nagios & Uptime Kuma—via a Webhook

Need to put monitored services into maintenance fast and reliably? This n8n workflow lets you request a maintenance window via webhook, then automatically creates downtime in Zabbix, schedules host downtime in Nagios over SSH, and pauses matching Uptime Kuma maintenances via its API.

What this workflow does

• Receives webhook requests containing one host (hostname/IP) or an array of hosts, plus maintenance start date/time, a service name, and downtime minutes.
• Validates and normalizes each entry, calculates start/end timestamps, and writes the maintenance details to an n8n Data Table.
• Processes hosts in batches and returns an OK response immediately to the webhook caller.
• For each host, looks up the Zabbix host ID and creates a Zabbix maintenance window for the computed time period.
• Stores the returned Zabbix maintenance ID back into the matching Data Table record.
• Schedules Nagios downtime by sending a command over SSH to the Nagios command file path configured for your installation.
• Pauses Uptime Kuma maintenances by fetching active maintenances, filtering by title matching the service name, and pausing them through the Uptime Kuma API.

Use cases

• Coordinate downtime for deployments or infrastructure changes spanning Zabbix, Nagios, and Uptime Kuma.
• Centralize maintenance scheduling for multiple hosts from a single automation endpoint (webhook trigger).
• Ensure consistent maintenance behavior during patch windows without manual UI steps.

Technical details

• Zabbix API: configure an n8n Zabbix API credential and ensure the API URL points to your Zabbix server.
• Nagios via SSH: add an SSH credential with permission to write to the Nagios command file (confirm the command path).
• Uptime Kuma API: add HTTP Bearer Auth and set the correct Kuma base URL.
• n8n nodes used: Webhook, Code, Merge, Data Table, HTTP Request, and SSH.