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 Container" resources. The "Create Web Trigger" operation allows users to create a new web trigger within the Commanders Act platform. This is useful for automating the setup of triggers that respond to specific web events or conditions in a tag management system.
Typical use cases include:
- Automating the creation of web triggers as part of a deployment pipeline.
- Dynamically managing web triggers based on external data or workflow logic.
- Integrating Commanders Act web container triggers into broader automation workflows.
For example, a marketing team could automatically create triggers that fire tags when certain user interactions occur on their website, without manual configuration in the Commanders Act interface.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional key-value pairs appended as URL query parameters to 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 request sent to create the web trigger. This contains the details of the web trigger to be created, such as its configuration and settings. |
The "Query Parameters" collection supports many optional fields, allowing fine control over the API call's filtering, sorting, and pagination behavior.
Output
The node outputs an array of JSON objects representing the response from the Commanders Act API after creating the web trigger. The structure depends on the API response but typically includes details of the newly created web trigger such as its ID, name, configuration, and status.
If the API returns no content, the output will indicate a "204 No Content" status.
The node does not output binary data.
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.
- The node uses standard HTTP methods (POST for creation) and JSON payloads.
Troubleshooting
- Missing Credentials: If the API credentials are not set or invalid, the node throws an error indicating missing credentials.
- Required Parameters Missing: For this operation, if required identifiers or parameters are missing (e.g., container ID or trigger details), the node throws an error specifying which parameter is required.
- API Errors: Any errors returned by the Commanders Act API are caught and rethrown with descriptive messages including the original error message and stack trace.
- Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors may occur.
- Unexpected Response Format: If the API returns a string response that cannot be parsed as JSON, the node attempts to return it as plain text.
To resolve issues:
- Ensure all required input properties are provided.
- Verify API credentials and permissions.
- Validate the JSON structure of the request body.
- Check network connectivity and API endpoint availability.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding HTTP method usage and JSON handling.
This summary focuses on the "Web Container" resource and the "Create Web Trigger" operation as requested.