Syncro RMM icon

Syncro RMM

Work with the Syncro RMM API

Actions19

Overview

The node interacts with the Syncro RMM API to retrieve multiple Alert records based on specified filters and limits. It is useful for scenarios where users want to fetch a list of alerts from their Syncro RMM environment, such as monitoring active or resolved alerts, or exporting alert data for reporting or further processing.

For example, a user might configure this node to:

  • Retrieve all active alerts to trigger notifications.
  • Fetch a limited number of recent alerts for dashboard display.
  • Filter alerts by status (active, resolved, or all) to analyze system health.

Properties

Name Meaning
Return All Whether to return all matching alert results or limit the number of results returned.
Limit The maximum number of alert results to return when "Return All" is false.
Filters Criteria to filter the alerts; currently supports filtering by Status: Active, Resolved, or All.

Filters Options Detail

  • Status: Select which alerts to retrieve based on their status.
    • Active: Only alerts that are currently active.
    • Resolved: Only alerts that have been resolved.
    • All: Both active and resolved alerts.

Output

The node outputs an array of alert objects in the json field of each item. Each alert object contains details about an individual alert retrieved from Syncro RMM, such as its status, timestamps, and other relevant metadata.

If binary data were involved, it would be summarized here, but this node focuses on JSON alert data only.

Dependencies

  • Requires an API key credential for authenticating with the Syncro RMM API.
  • Needs the Syncro RMM subdomain configured in credentials to construct the base URL.
  • The node depends on the Syncro RMM REST API being accessible and responsive.

Troubleshooting

  • Invalid API Key Error: If the API key is incorrect or expired, the node will fail authentication. Verify and update the API key credential.
  • Network Issues: Connectivity problems to the Syncro RMM API endpoint can cause request failures. Check network access and firewall settings.
  • Limit Exceeded: Setting a very high limit without enabling "Return All" may result in partial data. Use "Return All" to fetch complete datasets if needed.
  • Filter Misconfiguration: Using unsupported filter values may lead to empty results. Ensure the status filter is set to one of the allowed options.

Links and References

Discussion