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 Variables," specifically supporting the creation of web internal variables. It allows users to create new internal variables within web containers, which can be useful for managing and customizing data layers or internal tracking variables on websites.
Typical use cases include:
- Automating the creation of internal variables used in web tag management.
- Managing internal variables programmatically as part of a larger workflow involving web container configurations.
- Integrating variable creation into CI/CD pipelines for website analytics or tag management setups.
For example, a user might create an internal variable that holds session-specific data or user attributes to be used by other tags or scripts managed through Commanders Act.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional URL query parameters to customize the API request. Includes options like end, filter (with various sub-filters), granularity, include, page, sort, source, start, and a token (password type). |
| Request Body | JSON object representing the body of the POST request to create the web internal variable. This should contain the details of the internal variable to be created according to the Commanders Act API specification. |
Output
The node outputs the JSON response from the Commanders Act API after attempting to create the web internal variable. The output structure corresponds directly to the API's response and typically includes details about the newly created internal variable such as its ID, name, configuration, and status.
If the API returns no content (HTTP 204), the node outputs a JSON object indicating "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 node uses the base URL
https://api.commander1.com/v2. - Proper configuration of the API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Credentials: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials.
- Required Parameters Missing: The node validates required IDs or parameters depending on the operation. For creating web internal variables, ensure the request body is correctly provided.
- API Errors: Any errors returned by the Commanders Act API will be wrapped and thrown as node errors with messages prefixed by "Error calling Commanders Act API".
- Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors will occur.
- Network Issues: Connectivity problems to the API endpoint will cause request failures.
To resolve these issues:
- Verify API credentials are correctly configured.
- Ensure all required parameters and IDs are provided.
- Validate the JSON format of the request body.
- Check network connectivity and API availability.
Links and References
- Commanders Act API Documentation (official API docs)
- n8n Documentation (for general usage of HTTP Request nodes and credentials)