Datto RMM

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

Actions53

Overview

The "Get Device Audit" operation in the Audit resource retrieves audit information related to a specific device managed within Datto RMM. This node is useful for IT administrators and managed service providers who want to track changes, events, or historical data about devices under management. It can provide insights into device status, configuration changes, or other audit-related details.

Practical examples include:

  • Fetching recent audit logs for a device to investigate an incident.
  • Retrieving historical audit data within a specified date range for compliance reporting.
  • Including detailed audit information to get comprehensive context on device changes.

Properties

Name Meaning
Device Select the specific device to retrieve audit information for.
Include Archived Whether to include archived or historical audit data in the response.
Start Date (Optional) Start date filter for historical audit data when including archived data (ISO 8601 format).
End Date (Optional) End date filter for historical audit data when including archived data (ISO 8601 format).
Include Details Whether to include detailed audit information, which may increase the size of the response.
Fields to Include Select which fields to include in the response; supports adding all fields or selecting specific ones.

Output

The output JSON contains audit records for the selected device. Each record includes fields as specified by the "Fields to Include" property, potentially including timestamps, event types, user actions, and other audit metadata.

If "Include Details" is enabled, the output will contain more granular information per audit entry, which might increase the response size.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Datto RMM API with appropriate API authentication credentials configured in n8n.
  • The node depends on the Datto RMM API endpoints that provide device audit data.
  • The "Device" property options are dynamically loaded from the list of devices available via the API.

Troubleshooting

  • Common Issues:

    • Selecting a device that no longer exists or is not accessible may result in empty or error responses.
    • Requesting archived data without specifying valid start and end dates could lead to unexpected results or large payloads.
    • Enabling detailed audit information may cause performance issues or timeouts if the dataset is very large.

  • Error Messages:

    • Errors related to authentication typically indicate missing or invalid API credentials.
    • API rate limits or connectivity issues may cause request failures; ensure network access and API quota availability.
    • Invalid date formats for start/end dates should be corrected to ISO 8601 format.

Links and References

Discussion