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 enabling management of "Web Containers" among many other resources. The "Delete Web Container" operation allows users to delete a specified web container by its ID from their Commanders Act environment.
Use cases include:
- Automating cleanup or removal of obsolete or unused web containers.
- Managing web container lifecycle programmatically within workflows.
- Integrating container deletion as part of larger automation processes involving Commanders Act data governance or tag management.
Example: Automatically deleting a web container after archiving its data or when a project phase ends.
Properties
| Name | Meaning |
|---|---|
| Container ID | The unique identifier of the web container to delete. This is required for the delete operation. |
| Query Parameters | Optional additional parameters to customize the API request. Includes various filters and pagination options such as end, filter, page, sort, start, token, etc. |
The "Query Parameters" collection supports multiple optional fields that can be used to refine or control the API call, though for deletion typically only the Container ID is essential.
Output
The output is an array of JSON objects representing the response from the Commanders Act API after attempting to delete the web container.
- If the API returns a JSON response, it will be parsed and returned as JSON.
- If the API returns a string, the node attempts to parse it as JSON; if parsing fails, it returns the raw text.
- If no content is returned (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 in n8n is necessary before use.
Troubleshooting
- Missing Credentials: The node throws an error if the API credentials are not set up or missing.
- Missing Container ID: For the delete operation on web containers, the Container ID must be provided; otherwise, an error is thrown.
- API Errors: Any errors returned by the Commanders Act API are caught and rethrown with descriptive messages including the original error message and stack trace.
- Parsing Response: If the API returns unexpected non-JSON responses, the node tries to handle them gracefully but may output raw text.
To resolve issues:
- Ensure API credentials are correctly configured.
- Verify that the Container ID is correctly supplied.
- Check network connectivity and API endpoint availability.
- Review error messages for specific API error details.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes for further customization guidance