Local Hardware Monitor Trigger icon

Local Hardware Monitor Trigger

Trigger workflows based on local system metrics, hardware thresholds, network latency, or service failures

Local Hardware Monitor Trigger

AI-generated

Summary

Polls the machine running n8n for a selected hardware metric or system, network, or website condition, and emits an item when the configured condition is met. With “Only on State Transition,” it emits only when the condition first becomes true after being false; “Always” emits on every matching poll.

Inputs

  • Trigger Event Type (required) — Choose CPU load, CPU temperature, memory usage, disk utilization, Docker container state, OS service state, network latency, or website status.
  • Trigger Condition (required) — Choose whether to emit on every matching poll or only when the condition changes from false to true.
  • Threshold and comparison — For CPU temperature, CPU load, memory, or disk utilization, set the metric threshold and choose above or below. Defaults are 80 °C, 90%, 85%, and 90%, respectively. Disk checks use the configured mount path or drive identifier; if it does not match, the first reported partition is checked.
  • Container filters and event — For Docker checks, optionally enter a container name or ID prefix (blank checks any container) and choose starts running, stops running, or any state change.
  • Service name and event — For service checks, enter a service name and choose starts running, stops running, or any state change.
  • Latency host and condition — For network checks, specify a host to ping and trigger on ping failure or latency above a limit. The default host is 8.8.8.8 and the default limit is 150 ms.
  • Website URL and event — For website checks, specify an HTTP or HTTPS URL and trigger on any failure, a status code other than 200, or response time above a limit. The default URL is https://n8n.io and the default response time limit is 2000 ms.

Output shape

A single-item array containing one JSON item when a condition is met; otherwise no item is emitted.

The item includes the checked metric or state, relevant limit/comparison or prior state where applicable, a conditionMet flag, and a timestamp. Website check results also include URL, status code, and response time; connection failures report statusCode 0 and an error. Temperature data marked unavailable, unmatched disks or services, and unmatched containers produce no item. Docker state changes are tracked for the first matched container, and service state changes for the returned service.

Links

Discussion