Actions5
Overview
This node integrates with the CloudAlly API to retrieve backup status information, specifically for the "Backup Status" resource under the "Get Many" operation. It is designed to fetch multiple backup status records, which can be useful for monitoring and managing backups across different accounts or resellers.
Typical use cases include:
- Aggregating backup statuses for multiple clients or resellers.
- Automating backup health checks and reporting.
- Integrating backup status data into dashboards or alerting systems.
For example, a managed service provider could use this node to regularly pull backup statuses from all their reseller accounts to ensure backups are running smoothly.
Properties
| Name | Meaning |
|---|---|
| Resource Type | The type of resource to query. Options: "Reseller". This determines the API endpoint used. |
Output
The node outputs JSON data containing an array of backup status objects retrieved from the CloudAlly API. Each object represents the backup status details for a particular entity (e.g., a reseller). The exact structure depends on the API response but typically includes fields such as backup success/failure, timestamps, and related metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the CloudAlly API. This includes an access token, client ID, and client secret.
- The base URL for requests is dynamically set based on the selected resource type; for "Reseller," it uses
https://api.cloudally.com/v2/resellers. - Pagination support is included via a utility function to handle multiple pages of results.
Troubleshooting
- Authentication errors: Ensure that the API credentials (access token, client ID, client secret) are correctly configured and valid.
- API endpoint issues: Selecting an unsupported resource type or misconfiguration of the base URL may cause request failures.
- Pagination problems: If many records exist, incomplete data might be returned if pagination is not handled properly. The node includes pagination logic, but verify that it works as expected.
- Network errors: Check network connectivity and firewall settings that might block access to the CloudAlly API endpoints.
Links and References
- CloudAlly API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance