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 to manage web containers and other resources. Specifically, the "Update Web Container" operation allows users to update an existing web container's configuration by sending a PATCH request with the desired changes.
Use cases include:
- Modifying settings or metadata of a web container used for tag management or data collection on websites.
- Automating updates to web container configurations as part of deployment pipelines.
- Integrating web container management into broader workflows that involve website analytics or marketing tools.
Example: You have a web container deployed on your site and want to update its name or associated tags programmatically via n8n without manually logging into the Commanders Act platform.
Properties
| Name | Meaning |
|---|---|
| Container ID | The unique identifier of the web container to update. |
| Query Parameters | Optional additional parameters to customize the API request (e.g., filters, pagination). |
| Request Body | JSON object containing the fields and values to update in the web container. |
Details on Query Parameters
The query parameters are optional and can include various filters and options such as date ranges, sorting, pagination, and specific field selections. These allow fine-tuning of the API call but are not mandatory for the update operation.
Output
The node outputs the JSON response returned by the Commanders Act API after performing the update operation. This typically includes the updated web container object with its current properties reflecting the changes made.
If the API returns no content (HTTP 204), the output will indicate "Status Code": "204 No Content".
No binary data is produced by this node.
Dependencies
- Requires an active Commanders Act API credential with a valid site ID and API token.
- The node uses the base URL
https://api.commander1.com/v2for all requests. - Proper permissions on the API key are necessary to perform update operations on web containers.
Troubleshooting
- Missing Container ID: The node throws an error if the Container ID is not provided when attempting to update a web container. Ensure this property is set.
- Invalid JSON in Request Body: The request body must be valid JSON. Malformed JSON will cause the API call to fail.
- API Authentication Errors: If credentials are missing or invalid, the node will throw an authentication error. Verify the API token and site ID.
- Unknown Resource or Operation: Providing incorrect resource or operation names will result in errors. Confirm you are using "webContainers" as the resource and "webContainersContainersPatch" as the operation for updating web containers.
- API Rate Limits or Network Issues: Network failures or rate limiting by the API may cause errors. Retry or check API usage limits.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and payloads)
- Commanders Act Web Containers Management (specific details about web container endpoints)
This summary is based solely on static analysis of the provided source code and property definitions.