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 to manage monitoring alerts among other resources. Specifically, the "Update Alert" operation under the "Monitoring" resource allows users to update an existing alert by specifying its ID and providing updated data in the request body.
Use cases include automating alert management workflows such as modifying alert conditions or parameters programmatically within an n8n workflow. For example, you could update an alert's threshold or notification settings based on dynamic inputs or external triggers.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The unique identifier of the alert to update. |
| Query Parameters | Optional additional query parameters to customize the API request. |
| Request Body | JSON object containing the fields and values to update for the alert. |
The "Query Parameters" collection supports various optional parameters like end, filter, granularity, include, page, sort, source, start, and a token (password type). These allow fine-tuning of the API call but are generally not required for updating an alert.
Output
The node outputs the JSON response from the Commanders Act API after performing the update operation. This typically includes the updated alert object with its current properties reflecting the changes made.
If the API returns no content (HTTP 204), the output will indicate "Status Code": "204 No Content".
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used is
https://api.commander1.com/v2. - The node expects valid credentials configured in n8n to authorize requests.
Troubleshooting
- Missing Credentials: If the API key credential is not set or invalid, the node throws an error indicating missing credentials.
- Required Parameter Missing: If the Alert ID is not provided when updating an alert, the node throws an error stating that the Alert ID is required.
- API Errors: Any errors returned by the Commanders Act API during the request will be wrapped and reported as node API errors with details.
- Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors may occur.
To resolve these issues:
- Ensure the API key credential is correctly configured.
- Provide all required parameters, especially the Alert ID.
- Validate the JSON structure in the request body before execution.
Links and References
- Commanders Act API Documentation (official API reference)
- n8n documentation on HTTP Request Node for understanding API calls in workflows