Actions83
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Container Actions
Overview
This node integrates with the Commanders Act API, specifically providing management capabilities for various resources including Monitoring. The "Destroy Notification" operation under the Monitoring resource allows users to delete a specific notification by its ID. This is useful in scenarios where notifications related to alerts or monitoring events are no longer needed and should be removed to keep the system clean or to manage alert noise.
Practical example:
- Automatically remove outdated or resolved notifications from your monitoring dashboard to maintain clarity.
- Integrate with workflows that clean up monitoring notifications after certain conditions are met (e.g., after an incident is acknowledged).
Properties
| Name | Meaning |
|---|---|
| Notification ID | The unique identifier of the notification to be destroyed (deleted). |
| Query Parameters | Optional additional parameters to customize the request; includes filters, pagination, etc. |
The "Query Parameters" collection supports multiple optional fields such as:
- End, Start: Date/time boundaries for filtering.
- Filter: JSON object or specific filter keys like begin_date, end_date, search, segment_id, types, etc.
- Granularity, Include, Page, Sort, Source, Token: Various options to refine the API request.
Output
The output is a JSON array containing the response from the Commanders Act API after attempting to destroy the specified notification. Typically, this will confirm successful deletion or provide error details if the operation failed.
If the API returns no content (HTTP 204), the node outputs an 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/v2for all requests. - Proper configuration of the API credentials within n8n is necessary before use.
Troubleshooting
- Missing Notification ID: If the Notification ID property is not provided when required, the node throws an error stating "Notification ID is required".
- API Authentication Errors: Ensure the API key credential is correctly set up and valid; otherwise, authentication errors will occur.
- Invalid Notification ID: If the provided Notification ID does not exist or is invalid, the API may return an error which the node surfaces.
- Network Issues: Connectivity problems to the Commanders Act API endpoint can cause request failures.
- Unexpected API Responses: If the API returns unexpected data formats, parsing errors might occur.
To resolve these issues:
- Double-check the Notification ID input.
- Verify API credentials and permissions.
- Confirm network connectivity.
- Review API documentation for any changes in endpoints or parameters.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes