Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API, specifically supporting various resources and operations related to data management and monitoring within the Commanders Act platform. The "Monitoring" resource with the "Destroy Alert" operation allows users to delete an existing alert by its ID.

Use cases include automating alert management workflows such as removing obsolete or resolved alerts from the monitoring system. For example, after an alert condition is no longer relevant, this node can be used to programmatically destroy that alert to keep the monitoring dashboard clean and up-to-date.

Properties

Name Meaning
Alert ID The unique identifier of the alert to be destroyed (deleted). This is required for this operation.
Query Parameters Optional additional parameters to customize the request, such as filtering, pagination, sorting, date ranges, etc. These include options like end, filter, granularity, include, page, sort, source, start, and a password-type token.

Note: For this specific "Destroy Alert" operation, only the "Alert ID" is mandatory; query parameters are optional and may not affect the delete operation directly.

Output

The output of this node is the JSON response returned by the Commanders Act API after attempting to destroy the alert. Typically, a successful deletion might return a confirmation message or status code. If the API returns no content (HTTP 204), the node outputs a JSON object indicating "Status Code": "204 No Content".

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Commanders Act API.
  • The node uses the base URL https://api.commander1.com/v2 for all requests.
  • Proper configuration of the API credentials in n8n is necessary before using this node.

Troubleshooting

  • Missing Alert ID: The node will throw an error if the "Alert ID" property is empty when performing the destroy operation. Ensure you provide a valid alert ID.
  • Authentication Errors: If the API credentials are missing or invalid, the node will raise an error indicating missing credentials or authorization failure.
  • API Request Failures: Network issues or incorrect API endpoint usage may cause errors. The node surfaces these as API errors with messages and stack traces.
  • Unexpected Response Format: If the API returns a non-JSON string or empty response, the node attempts to parse it but falls back to returning raw text or a status code message.

To resolve common errors:

  • Verify the alert ID exists and is correct.
  • Confirm API credentials are set and have sufficient permissions.
  • Check network connectivity and API availability.
  • Review error messages for specific details on failures.

Links and References

Discussion