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 container variables, specifically allowing users to create a new category for web datalayer variables. It is useful in scenarios where you want to organize or categorize data layer variables used in web containers for tag management or analytics purposes. For example, if you are managing multiple data layer variables on your website and want to group them logically (e.g., by user behavior, e-commerce data, or marketing campaigns), this operation helps create such categories programmatically.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional URL query parameters to customize 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 POST request to create the web datalayer variable category. This should contain the details of the category to be created. |
Output
The output is a JSON array containing the response from the Commanders Act API after creating the web datalayer variable category. The structure depends on the API's response but typically includes details of the newly created category such as its ID, name, description, and other metadata.
If the API returns no content, the node outputs a status code message indicating "204 No Content".
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL for API requests is
https://api.commander1.com/v2. - The node expects valid credentials configured in n8n to authorize API calls.
Troubleshooting
- Missing Credentials: If the API credentials are not set or invalid, the node will throw an error "Missing Commanders Act API Credentials". Ensure that the API key/token is correctly configured.
- Required Parameters Missing: The node checks for required IDs or parameters depending on the operation. For this operation, ensure the request body is properly formed JSON; otherwise, the API call may fail.
- API Errors: Any errors returned by the Commanders Act API will be wrapped and thrown as node errors with messages like "Error calling Commanders Act API: [error message]". Check the API documentation and verify the request payload and parameters.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON will cause parsing errors before sending the request.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n Documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.