Monitor n8n Container Health with Uptime Kuma

Running n8n without external health monitoring means you learn about outages when users report them. Uptime Kuma is a self-hosted monitor that checks your instance's health endpoint, editor reachability, and webhook responsiveness, then alerts you through Slack, email, or PagerDuty within seconds. Three monitors covering these failure modes catch most outage types within 30 to 60 seconds.

Why monitor n8n with Uptime Kuma?

Running n8n without external health monitoring means you discover outages when users report them. Uptime Kuma is a self-hosted monitoring tool that can check your n8n instance's health endpoint, editor reachability, and webhook responsiveness, then alert you via Slack, email, or PagerDuty within seconds of a failure.

How do you set up the monitors?

Real-world example: You deploy Uptime Kuma alongside n8n and configure three monitors: the health endpoint, the editor page, and a test webhook.

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    restart: unless-stopped
    ports:
      - "3001:3001"
    volumes:
      - uptime_kuma_data:/app/data
    networks:
      - monitoring

volumes:
  uptime_kuma_data:

networks:
  monitoring:
    driver: bridge

Once Uptime Kuma is running, configure the following monitors through its web UI:

Monitor 1 - Health Endpoint:
  Type:     HTTP(s)
  URL:      https://n8n.example.com/healthz
  Interval: 30 seconds
  Retries:  3
  Alert:    Slack webhook

Monitor 2 - Editor Reachable:
  Type:     HTTP(s) - Keyword
  URL:      https://n8n.example.com/
  Keyword:  n8n
  Interval: 60 seconds
  Alert:    Slack webhook

Monitor 3 - Webhook Processing:
  Type:     HTTP(s)
  URL:      https://n8n.example.com/webhook-test/health-check
  Method:   POST
  Body:     {"ping": true}
  Expected: 200
  Interval: 300 seconds
  Alert:    Slack webhook + Email

With three monitors covering different failure modes, you will be alerted within 30-60 seconds of most outage types.

What does the /healthz endpoint actually check?

Note: The /healthz Endpoint

n8n exposes /healthz which returns HTTP 200 when the application is running. This checks the application process but does not verify database connectivity. For deeper health checks, use Monitor 3 with a dedicated health-check workflow that queries the database.

Related: Set a Unique Encryption Key and Back It Up · Configure Payload Size and Binary Data Mode for Large Files