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, specifically allowing users to update a Web Trigger within the "Web Container" resource. It performs an HTTP PATCH request to modify properties of an existing web trigger identified by its Trigger ID.
Use cases include managing and updating configurations for web triggers in your Commanders Act account, such as changing trigger conditions or metadata. This is useful for marketers or developers who want to automate updates to their web tracking setup without manually accessing the Commanders Act platform.
Example: Automatically update a web trigger's settings based on external events or data changes, enabling dynamic control over website tag management.
Properties
| Name | Meaning |
|---|---|
| Trigger ID | The unique identifier of the web trigger to update (required). |
| Query Parameters | Optional additional query parameters to customize the API request. Includes options like end, filter, page, sort, start, token, etc. These allow filtering, pagination, sorting, and authentication token overrides. |
| Request Body | JSON object containing the fields and values to update on the web trigger. This is the main payload sent in the PATCH request to modify the trigger's properties. |
Output
The node outputs the JSON response from the Commanders Act API after updating the web trigger. The output structure corresponds directly to the API's response schema for the updated web trigger resource, typically including updated trigger details such as IDs, names, conditions, and other configuration data.
If the API returns no content (HTTP 204), the node outputs a status message indicating "204 No Content".
No binary data output is involved.
Dependencies
- Requires an active Commanders Act API credential with a valid site ID and API token.
- The node makes HTTPS requests to the Commanders Act API endpoint at
https://api.commander1.com/v2. - Proper network connectivity and permission to access the Commanders Act API are necessary.
Troubleshooting
- Missing Trigger ID: If the Trigger ID is not provided, the node will throw an error stating that the Trigger ID is required. Ensure this property is set.
- Invalid JSON in Request Body: The Request Body must be valid JSON. Malformed JSON will cause parsing errors.
- Authentication Errors: Missing or invalid API credentials will result in authorization failures. Verify that the API token and site ID are correctly configured.
- API Errors: Any errors returned by the Commanders Act API (e.g., invalid parameters, resource not found) will be surfaced as node errors with descriptive messages.
- Network Issues: Connectivity problems may cause request failures; check network access and proxy settings if applicable.
Links and References
- Commanders Act API Documentation (for detailed API reference and examples)
- n8n Documentation (for general usage of n8n nodes and credentials)