Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API, allowing users to manage various resources related to web containers, activity logs, consent analysis, cookie scanning, data cleansing, destinations, event delivery, event enrichment, live reports, monitoring, segments, sources, users, workspaces, and more.

Specifically for the Web Container resource and the Delete Web Perimeter operation, this node enables the deletion of a specified web perimeter within a web container setup. This is useful in scenarios where you want to programmatically remove perimeter configurations that define boundaries or rules for web tracking or tag management.

Practical examples include:

  • Automating cleanup of outdated or unused web perimeters.
  • Managing web container configurations dynamically based on business logic.
  • Integrating perimeter deletion into larger workflows for website tag management or compliance.

Properties

Name Meaning
Perimeter ID The unique identifier of the web perimeter to delete.
Query Parameters Optional additional parameters to customize the API request. Includes options like:
- End, Start (date/time strings)
- Fields[template] (string)
- Filter (JSON or specific filter fields such as begin_date, end_date, search, segment_id)
- Granularity (string)
- Include (string)
- Page (JSON)
- Sort (JSON or string)
- Source (string)
- Token (password type string)

These query parameters allow fine-tuning of the API call, although for deletion they might be less commonly used.

Output

The output is a JSON array containing the response from the Commanders Act API after attempting to delete the specified web perimeter. The structure depends on the API's response but typically includes status information or confirmation of deletion.

If the API returns no content (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 active connection to the Commanders Act API.
  • Requires valid API credentials including a site ID and an API token.
  • The node uses HTTP requests to https://api.commander1.com/v2 endpoint.
  • Proper configuration of the API credentials in n8n is necessary before use.

Troubleshooting

  • Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials.
  • Required Parameter Missing: If the Perimeter ID is not provided when performing the delete operation, the node throws an error stating that the Perimeter ID is required.
  • API Errors: Any errors returned by the Commanders Act API during the delete request will be caught and reported with details.
  • Invalid Query Parameters: Providing malformed or unsupported query parameters may cause the API to reject the request.
  • Network Issues: Connectivity problems to the Commanders Act API endpoint will result in request failures.

To resolve these issues:

  • Ensure API credentials are correctly configured.
  • Provide all required parameters, especially the Perimeter ID.
  • Validate any query parameters used.
  • Check network connectivity and API availability.

Links and References

Discussion