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, allowing users to manage various resources related to web containers and other platform features. Specifically, for the Web Container resource and the Delete Web Constraint operation, it enables deleting a specific web constraint by its ID. This is useful in scenarios where you need to programmatically remove constraints that control or restrict certain behaviors within web containers managed by Commanders Act.
Practical examples include:
- Automating cleanup of obsolete or invalid web constraints.
- Managing web container configurations dynamically based on changing business rules.
- Integrating with workflows that require conditional removal of constraints as part of deployment or maintenance processes.
Properties
| Name | Meaning |
|---|---|
| Constraint ID | The unique identifier of the web constraint to delete. This is required to specify which constraint to remove. |
| Query Parameters | Optional additional parameters to customize the API request. Includes options like end, filter, page, sort, start, 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(and nested filters): JSON or string filters for refined queries.page: Pagination details.sort: Sorting instructions.token: An optional token for authentication or session purposes.
Output
The node outputs the response from the Commanders Act API after attempting to delete the specified web constraint. The output is a JSON array where each item corresponds to the API response for each input item processed.
- If the deletion is successful and the API returns data, the JSON will contain that data.
- If the API returns no content (HTTP 204), the output will indicate
"Status Code": "204 No Content". - If the response is a string, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires 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 Credentials Error: If the API credentials are not set or invalid, the node throws an error indicating missing credentials. Ensure the API key/token and site ID are correctly configured.
- Missing Constraint ID: The node requires the
Constraint IDproperty for this operation. Omitting it results in an error prompting to provide this ID. - API Errors: Any errors returned by the Commanders Act API during the delete request are caught and rethrown with descriptive messages. Check the API documentation and ensure the constraint ID exists and the user has permission to delete it.
- Unexpected Response Format: If the API returns a non-JSON response, the node tries to handle it gracefully but may output raw text. Verify API status and connectivity.
Links and References
- Commanders Act API Documentation (official API base URL referenced in code)
- For detailed API usage and available endpoints, consult the Commanders Act developer portal or support resources.