Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
This node interacts with the Datto RMM (Remote Monitoring and Management) API to retrieve system-related information, specifically focusing on rate limit data in this context. The "Get Rate Limit" operation under the "System" resource allows users to query the current or historical API usage limits and consumption. This is useful for monitoring API quota usage to avoid hitting limits that could disrupt automation workflows.
Practical examples include:
- Checking the current API rate limit status before making bulk requests.
- Analyzing API usage trends over the last hour, day, or week to optimize request scheduling.
- Including detailed usage history to understand peak usage times and adjust integrations accordingly.
Properties
| Name | Meaning |
|---|---|
| Time Period | Selects the time frame for rate limit analysis. Options: Current, Last Hour, Last Day, Last Week. |
| Include Usage History | Boolean flag to include detailed historical usage data and trends in the response. |
| Fields to Include | Allows selection of specific fields to include in the response, enabling customization of output. |
Output
The node outputs JSON data containing the rate limit information for the selected time period. This includes details such as the maximum allowed requests, remaining requests, reset times, and optionally, historical usage trends if requested.
If binary data were involved (not indicated here), it would typically represent files or attachments related to the API response, but this node focuses solely on JSON structured data.
Dependencies
- Requires an active connection to the Datto RMM API via a configured API key credential.
- The node depends on proper API URL configuration within the credentials.
- No additional external services are required beyond the Datto RMM API.
Troubleshooting
Common Issues:
- Incorrect or expired API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
- Requesting unsupported time periods or invalid field selections may result in errors.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- Rate limit exceeded errors suggest too many requests; consider increasing intervals between calls or reviewing usage patterns.
- Field selection errors occur if requested fields do not exist; ensure correct field names are used.