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, enabling users to manage various resources related to digital marketing and data governance. Specifically, for the Web Container resource with the List Web Containers operation, it allows retrieving a list of web containers configured in the Commanders Act platform.
Use cases include:
- Fetching all web containers to audit or synchronize container configurations.
- Automating workflows that depend on the current state or metadata of web containers.
- Integrating container data into broader analytics or tag management processes.
For example, a marketing automation workflow might use this node to pull the latest web container configurations before deploying updates or generating reports.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to filter, sort, paginate, or specify fields in the list request. Possible keys include: end, Fields[template], filter (and nested filters like begin_date, end_date, search, etc.), granularity, include, page, sort, source, start, and token. These allow fine-tuning the list query to retrieve specific subsets or views of web containers. |
The "Query Parameters" property supports multiple options such as date ranges, filtering by device or location, sorting criteria, pagination, and token-based access control.
Output
The node outputs an array of JSON objects representing the web containers retrieved from the Commanders Act API. Each object corresponds to a web container's data as returned by the API.
- The output is structured as JSON under the
jsonfield. - If the API returns no content, the node outputs a status message indicating "204 No Content".
- The node does not output binary data for 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 containing a site ID and an API token.
- No additional external dependencies are required beyond the API access.
Troubleshooting
- Missing Credentials Error: If the API credentials are not provided or invalid, the node throws an error indicating missing credentials. Ensure the API key and site ID are correctly configured in n8n.
- Required Parameter Missing: For some operations, certain IDs or parameters are mandatory. For listing web containers, ensure any required query parameters are correctly set if needed.
- API Errors: If the API call fails, the node throws an error with the message prefixed by "Error calling Commanders Act API". Check the API token validity, network connectivity, and parameter correctness.
- Empty Response: A "204 No Content" response means no web containers matched the query. Adjust filters or verify the existence of containers in the Commanders Act platform.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and parameters)
- n8n Documentation - Creating Custom Nodes
- Commanders Act Official Website
This summary focuses on the Web Container resource and the List Web Containers operation, describing how the node constructs the API request, handles input properties, and formats the output accordingly.