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 a specific device by its numeric ID. It is useful in scenarios where you need to fetch device details for monitoring, reporting, or automation workflows within IT management processes. For example, you might use this node to get the current status, configuration, or other metadata of a device managed in Datto RMM to trigger alerts, update inventories, or integrate with other systems.

Properties

Name Meaning
Device ID The numeric identifier of the device you want to retrieve information for.
Fields to Return Select which fields of the device record to include in the response (customizable output).

Output

The node outputs JSON data representing the device's details as returned by the Datto RMM API. The structure includes all requested fields about the device, such as hostname, IP address, device type, status, and other metadata depending on the selected fields. This allows downstream nodes to access specific device attributes for further processing.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
  • The node depends on the base URL and authentication headers set up in the credentials.
  • Network connectivity to the Datto RMM service endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Device ID will cause the API request to fail or return no data.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network issues or incorrect base URL configuration can prevent successful API calls.

  • Error Messages:

    • "Resource device is not supported yet." — indicates the resource parameter was set incorrectly; ensure "device" is selected.
    • API authentication errors typically indicate invalid credentials; verify and update your API key.
    • If the device ID does not exist, the API may return a 404 error; confirm the device ID is correct.

Links and References

Discussion