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 allowing management of various resources within the platform. For the Web Container resource and the Delete Web Trigger operation, it enables users to delete a specific web trigger by its ID. This is useful in scenarios where you want to programmatically remove triggers that are no longer needed or were created erroneously.
Practical examples include:
- Automating cleanup of outdated or test web triggers in your Commanders Act environment.
- Managing web triggers dynamically based on external events or workflows.
- Integrating trigger deletion as part of a larger container or tag management automation.
Properties
| Name | Meaning |
|---|---|
| Trigger ID | The unique identifier of the web trigger to delete. This is required for the delete operation. |
| Query Parameters | Optional additional parameters to customize the API request. Includes options like end, filter, page, sort, start, token (API token), and others for filtering or pagination. |
The "Query Parameters" collection supports multiple optional fields such as:
end,start: Date/time boundaries for filtering.filter: JSON object or string for complex filtering.page: JSON for pagination control.sort: JSON or string to specify sorting order.token: A password-type field for an API token if needed.
Output
The node outputs the JSON response from the Commanders Act API after attempting to delete the specified web trigger. The output structure depends on the API's response but typically includes confirmation of deletion or error details.
If the API returns no content (HTTP 204), the node outputs a JSON object with "Status Code": "204 No Content" indicating successful deletion without additional data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Needs valid API credentials including a site ID and an API token.
- The node expects these credentials to be configured in n8n prior to execution.
Troubleshooting
- Missing Trigger ID: If the Trigger ID is not provided, the node will throw an error stating that the Trigger ID is required.
- Authentication Errors: If API credentials are missing or invalid, the node will raise an error about missing credentials or failed authentication.
- API Errors: Any errors returned by the Commanders Act API (e.g., trigger not found, permission denied) will be surfaced as node errors with descriptive messages.
- Invalid Query Parameters: Providing malformed JSON or unsupported query parameters may cause the API call to fail.
To resolve issues:
- Ensure the Trigger ID is correctly set.
- Verify API credentials and permissions.
- Check the format and validity of any query parameters.
- Review the error message and stack trace provided by the node for debugging.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes
- Best practices for managing web triggers in Commanders Act (refer to official Commanders Act guides)
This summary focuses exclusively on the Web Container resource and the Delete Web Trigger operation as requested.