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 various resources related to digital marketing and data governance. Specifically, for the Event Enrichment resource with the Destroy Event Enrichment operation, it allows users to delete a specific event enrichment by its ID.
Use cases include:
- Removing outdated or incorrect event enrichment configurations from your Commanders Act account.
- Automating cleanup of event enrichments as part of a larger workflow managing event data.
- Managing event enrichments programmatically without manual intervention in the Commanders Act dashboard.
Example scenario: You have an event enrichment that is no longer relevant due to changes in your data strategy. Using this node, you can delete that enrichment automatically when triggered by certain conditions in your workflow.
Properties
| Name | Meaning |
|---|---|
| Event Enrichment ID | The unique identifier of the event enrichment to be deleted. This is required for the destroy operation. |
| Query Parameters | Optional additional parameters to customize the API request. Includes options like filters, pagination, sorting, date ranges, etc. (various keys such as end, filter[begin_date], page, sort, etc.) |
The "Query Parameters" collection supports many optional fields to refine the request, but for the destroy operation, typically only the Event Enrichment ID is mandatory.
Output
The output is a JSON array containing the response from the Commanders Act API after attempting to delete the specified event enrichment.
- If the deletion is successful, the API may return confirmation data or a status code indicating success.
- If there is no content returned (HTTP 204), the node outputs a JSON object with
"Status Code": "204 No Content". - In case of errors, the node throws an error with details about the failure.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Users must provide valid API credentials (an API token and site ID) configured in n8n.
- The node uses HTTP requests to the Commanders Act API endpoint
https://api.commander1.com/v2.
Troubleshooting
- Missing Event Enrichment ID: The node will throw an error if the Event Enrichment ID is not provided for operations that require it (like destroy). Ensure this property is set.
- Authentication Errors: If API credentials are missing or invalid, the node will fail with an authentication error. Verify that the API token and site ID are correctly configured.
- API Request Failures: Network issues or invalid parameters may cause the API call to fail. Check the error message for details and verify the correctness of input parameters.
- Unexpected Response Format: If the API returns unexpected data, the node attempts to parse it as JSON; if parsing fails, it returns raw text. This usually indicates an issue with the API or request.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n Documentation - Creating Custom Nodes
- Commanders Act Event Enrichments API Reference (for detailed API specs on event enrichment management)