Actions108
- 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
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Tag
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Overview
This node integrates with the Commanders Act API, specifically enabling management of various resources within the platform. The "Destroy Destination" operation under the "Destination" resource allows users to delete a specific destination integration from their Commanders Act environment.
This operation is useful when you want to programmatically remove an existing destination integration that is no longer needed or was created by mistake. For example, if you have multiple marketing or analytics destinations configured and want to clean up unused ones automatically, this node operation can be used in workflows to delete those destinations by their ID.
Properties
| Name | Meaning |
|---|---|
| Destination ID | The unique identifier of the destination to be deleted. This is required for deletion. |
| Query Parameters | Optional additional parameters to customize the API request. Includes options like: End, Fields[template], Filter (with sub-options), Granularity, Include, Page, Sort, Source, Start, Token (API token). |
The "Query Parameters" collection supports many optional filters and pagination controls, but for the destroy operation, these are typically not necessary unless the API requires them for some reason.
Output
The output JSON contains the response from the Commanders Act API after attempting to delete the specified destination. Typically, a successful delete operation returns a status code indicating success (e.g., 204 No Content) or a confirmation message.
- If the API returns a JSON response, it will be parsed and returned as JSON.
- If the response is empty or a plain string, it will be returned as text or a status code message.
- No binary data output is expected for 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 in n8n is mandatory before using this node.
Troubleshooting
- Missing Destination ID: The node throws an error if the Destination ID is not provided for the destroy operation. Ensure you specify the correct ID.
- Authentication Errors: If the API key credential is missing or invalid, the node will fail with an authentication error. Verify your API credentials.
- API Errors: Any errors returned by the Commanders Act API (such as trying to delete a non-existent destination) will be surfaced as node errors with descriptive messages.
- Empty Response: A 204 No Content response indicates successful deletion without additional data; this is normal behavior.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes for further customization guidance