PaperCut Health API icon

PaperCut Health API

Interact with the PaperCut MF / NG health monitoring api
Join our community

Actions10

Overview

This node interacts with the PaperCut MF / NG health monitoring API, specifically targeting the "Status" resource and its "Web Print Servers" operation. It is designed to check the status of web print servers within a PaperCut environment, allowing users to monitor server health and identify issues based on configurable error thresholds.

Common scenarios:

  • Monitoring the operational status of web print servers in real-time.
  • Setting up automated alerts or workflows if too many servers are in an error state.
  • Integrating PaperCut server health checks into broader IT monitoring dashboards.

Practical example:
A system administrator can use this node in an n8n workflow to periodically check if the number of web print servers in error exceeds a certain threshold, triggering notifications or remediation steps if problems are detected.

Properties

Name Type Meaning
Servers In Error Threshold Number Threshold for allowed server errors. If the number of servers in error exceeds this value, it may trigger specific actions or responses in the workflow.

Output

The node outputs a json field containing the response from the PaperCut Health API regarding the status of web print servers. The exact structure depends on the API's response, but typically includes information about each server's status and whether the error threshold has been exceeded.

If the node supports binary output, it would summarize the health data, but for this operation, only JSON output is expected.

Dependencies

  • External Service: Requires access to a running instance of the PaperCut MF / NG health monitoring API.
  • API Credentials: Needs valid credentials (paperCutHealthApi) configured in n8n, including:
    • domain: Base URL of the PaperCut server.
    • selfSigned: Boolean indicating if SSL certificate validation should be skipped (for self-signed certificates).

Troubleshooting

Common Issues:

  • Invalid Credentials: If the provided API credentials are incorrect or missing, authentication will fail.
  • Network Errors: Connectivity issues between n8n and the PaperCut server can prevent successful API calls.
  • Threshold Misconfiguration: Setting the "Servers In Error Threshold" too low or high may result in missed alerts or false positives.

Common Error Messages:

  • 401 Unauthorized: Check your API credentials.
  • Connection Refused/Timeout: Ensure the PaperCut server is reachable from your n8n instance.
  • Invalid Parameter: Make sure "Servers In Error Threshold" is set to a valid number.

Links and References

Discussion