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 Tag" operation allows users to create a new web tag within the Commanders Act platform. This is useful for managing tags that track user interactions or other web-related events on websites.
Typical use cases include:
- Automating the creation of tracking tags for marketing or analytics purposes.
- Managing web tags programmatically as part of a larger workflow for website data governance.
- Integrating tag creation into CI/CD pipelines for web projects.
For example, a marketing team could use this node to automatically deploy new tracking tags when launching campaigns, ensuring consistent and error-free tag management.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional URL query parameters to customize the API request. Includes various filters and pagination options such as end, filter[begin_date], page, sort, etc. |
| Request Body | JSON object representing the body of the HTTP request. For creating a web tag, this contains the details of the tag to be created. |
The "Query Parameters" collection supports multiple optional fields like date filters, sorting, pagination, and token authentication. The "Request Body" must be a valid JSON describing the web tag attributes according to the Commanders Act API specification.
Output
The node outputs an array of JSON objects representing the response from the Commanders Act API after creating the web tag. The structure depends on the API's response but typically includes details of the newly created web tag such as its ID, name, configuration, and status.
If the API returns no content (HTTP 204), the output will indicate "Status Code": "204 No Content".
No binary data output is produced by this node.
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 the API token and site ID to be provided via credentials configured in n8n.
- 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 Parameter Missing: If mandatory parameters like container ID or tag ID are missing when required, the node throws an error specifying which parameter is missing.
- API Errors: Any errors returned by the Commanders Act API are wrapped and rethrown as node API errors with descriptive messages.
- 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 that cannot be parsed as JSON, the node attempts to return it as plain text.
To resolve issues:
- Ensure all required parameters for the operation are provided.
- Verify API credentials and permissions.
- Validate the JSON format of the request body.
- Check network connectivity and API endpoint availability.
Links and References
- Commanders Act API Documentation (official API docs)
- n8n Documentation - Creating Custom Nodes
- Commanders Act Web Container API Reference (for detailed schema of web tags)