Datto RMM

Interact with Datto RMM API to manage devices, sites, alerts, and monitoring

Actions53

Overview

This node interacts with the Datto RMM API to retrieve detailed information about jobs and their components within a managed environment. Specifically, the "Get Components" operation under the "Job" resource fetches the list of components associated with jobs available in the Datto RMM account.

This node is beneficial for IT administrators or managed service providers who want to automate monitoring or reporting on job components executed in their remote monitoring and management system. For example, it can be used to gather component details for audit purposes, troubleshooting job executions, or integrating job data into other workflows.

Properties

Name Meaning
Job Select the specific job from the list of available jobs to retrieve its components. The options are dynamically loaded from the current jobs in the Datto RMM account.

Output

The node outputs JSON data representing the components related to the selected job. Each item in the output corresponds to a component with fields such as its unique identifier, name, description, and potentially other metadata provided by the Datto RMM API.

If binary data were involved (e.g., logs or files), it would be summarized here, but this operation focuses on JSON component data only.

Dependencies

  • Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
  • The node depends on the Datto RMM API endpoints to fetch jobs and their components.
  • Network access to the Datto RMM API base URL must be configured correctly in the node credentials.

Troubleshooting

  • Common issues:
    • Failure to load jobs or components often results from incorrect API credentials or network connectivity problems.
    • Selecting a job that no longer exists or has been deleted may cause empty results or errors.
  • Error messages:
    • Errors indicating unauthorized access usually mean the API key is invalid or lacks required permissions.
    • Timeout or network errors suggest connectivity issues between n8n and the Datto RMM API.
  • Resolutions:
    • Verify and update the API key credential in n8n.
    • Ensure the Datto RMM API URL is reachable from the n8n instance.
    • Confirm the selected job UID is valid and currently exists in the Datto RMM account.

Links and References

Discussion