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 "Create Web Container" operation allows users to create a new web container within their Commanders Act environment. This is useful for organizing and managing tags, triggers, and other web-related configurations in a centralized manner.
Practical scenarios include:
- Automating the creation of web containers as part of a deployment pipeline.
- Managing multiple web containers programmatically for different websites or environments.
- Integrating Commanders Act web container management into broader workflows that involve tag management or data collection.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional URL query parameters to customize the API request. Includes options like end, filter, granularity, page, sort, start, token (API token), and others for filtering and pagination. |
| Request Body | JSON object representing the body of the HTTP POST request to create the web container. This contains the details of the web container to be created, such as its configuration and metadata. |
The "Query Parameters" property supports multiple sub-options allowing fine control over the request, including date filters, sorting, pagination, and token overrides.
Output
The node outputs the JSON response from the Commanders Act API after creating the web container. The output structure corresponds directly to the API's response schema for a created web container, typically including identifiers, status, and any metadata returned by the API.
If the API returns a string response, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text. If no content is returned (HTTP 204), it outputs a status message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used is
https://api.commander1.com/v2. - The node expects valid credentials configured in n8n for accessing the Commanders Act API.
- The user must have appropriate permissions in Commanders Act to create web containers.
Troubleshooting
- Missing Credentials: The node will throw an error if the required API credentials are not provided. Ensure the API key credential is set up correctly in n8n.
- Required Parameter Missing: If mandatory parameters like container ID (for update/delete) or other IDs are missing when required, the node throws descriptive errors. For creation, ensure the request body is properly formed.
- API Errors: Any errors returned by the Commanders Act API are wrapped and rethrown with additional context. Check the error message and stack trace for details.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON will cause parsing errors before the API call.
- Network Issues: Connectivity problems to the API endpoint will result in request failures. Verify network access and API availability.
Links and References
- Commanders Act API Documentation (official API docs for detailed resource and operation info)
- n8n Documentation (for general usage of custom nodes and credentials setup)