Actions19
Overview
This node integrates with the Syncro RMM API to create an alert within the system. It is designed to facilitate automated alert creation based on asset, customer, or monitoring check data. Typical use cases include triggering alerts when specific conditions are met in IT infrastructure monitoring, such as detecting issues on assets or customer environments.
For example, you might use this node to automatically generate an alert when a particular asset fails a health check or when a customer reports an issue that requires tracking.
Properties
| Name | Meaning |
|---|---|
| Asset ID | The identifier of the asset related to the alert. |
| Customer ID | The identifier of the customer associated with the alert. |
| Check Type | The type of check or monitoring that triggered the alert (e.g., disk space, CPU usage). |
| Description | A textual description providing details about the alert. |
| Additional Fields | Optional extra fields for the alert; currently supports: |
| - Resolved | Boolean flag indicating whether the alert has been resolved (true or false). |
Output
The node outputs JSON data representing the created alert object as returned by the Syncro RMM API. This typically includes all relevant alert details such as IDs, timestamps, status, and descriptive information.
If the node supports binary data output, it would represent any associated files or attachments related to the alert, but based on the provided code and properties, the primary output is structured JSON data describing the alert.
Dependencies
- Requires an active connection to the Syncro RMM API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for API requests is dynamically constructed using the user's Syncro subdomain.
- The node depends on internal modules handling routing and API transport but no external npm packages beyond those bundled.
Troubleshooting
- Invalid API Key: If the API key is incorrect or expired, the node will fail authentication. The error message will indicate invalid credentials. To resolve, verify and update the API key in the node's credential settings.
- Missing Required Fields: Ensure that mandatory fields like Asset ID or Customer ID are correctly set; otherwise, the API may reject the request.
- Network Issues: Connectivity problems to the Syncro RMM service can cause timeouts or failures. Verify network access and Syncro service availability.
- Incorrect Resource/Operation Selection: Make sure the resource is set to "Alert" and operation to "Create" to match the expected input properties and functionality.
Links and References
- Syncro RMM API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes