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 supporting the "Cookie Scanner" resource and its operations. The "Create Generated Version" operation allows users to create a new generated version within the Cookie Scanner module of Commanders Act. This is useful for managing cookie compliance versions on websites, enabling automated updates or versioning of cookie scanner configurations.
Practical scenarios include:
- Automating the creation of new cookie scanner versions after updating cookie policies.
- Integrating cookie compliance workflows into broader automation pipelines.
- Managing multiple versions of cookie scanner configurations programmatically.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional query parameters to customize the API request. Includes options such as: End, Fields[template], Filter (with subfields like begin_date, end_date, search, segment_id, device, location, types), Granularity, Include, Page, Sort, Source, Start, Token (API token). These parameters allow filtering, sorting, pagination, and authentication customization. |
| Request Body | JSON object representing the body of the POST request to create the generated version. This contains the data required by the API to define the new generated version. |
Output
The node outputs the JSON response from the Commanders Act API corresponding to the created generated version. The output is an array of JSON objects representing the API response data. If the API returns no content, it outputs a status code message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used for requests is
https://api.commander1.com/v2. - The node expects valid credentials containing a site ID and an API token.
- 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 "Missing Commanders Act API Credentials". Ensure that the API key and site ID are correctly configured.
- Required Parameters Missing: For this operation, if required parameters such as the request body are missing or malformed, the API may return errors. Validate the input JSON structure.
- 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". Check the error message and stack trace for details.
- Invalid Query Parameters: Incorrect or unsupported query parameters may cause the API to reject the request. Use only supported parameters as defined.
- Network Issues: Connectivity problems to the API endpoint will result in request failures. Verify network access and proxy settings if applicable.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- Commanders Act Cookie Scanner Documentation (for detailed info on cookie scanner features and generated versions)
This summary focuses on the "Cookie Scanner" resource and the "Create Generated Version" operation as requested, based on static analysis of the provided source code and property definitions.