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 various resources and operations related to data management and privacy compliance. The "Cookie Scanner" resource's "Get Cookie" operation retrieves detailed information about a specific cookie managed by the Commanders Act platform.
Use cases include:
- Fetching metadata and configuration details of a particular cookie used on a website.
- Auditing cookies for compliance with privacy regulations.
- Integrating cookie data into workflows for reporting or further processing.
For example, a marketing team could use this node to automatically retrieve cookie details before generating a compliance report or updating cookie consent banners.
Properties
| Name | Meaning |
|---|---|
| Cookie ID | The unique identifier of the cookie to retrieve. This is required to specify which cookie's information should be fetched. |
| Query Parameters | Optional additional parameters to customize the request. These include: - End - Fields[template] - Filter (JSON) - Filter[begin_date] - Filter[end_date] - Filter[from] - Filter[rangeType] - Filter[search] - Filter[segment_id] - Filter[sup_filters][device][] - Filter[sup_filters][location][] - Filter[to] - Filter[types] - Granularity - Include - Page (JSON) - Sort (JSON or string) - Source - Start - Token (password type) |
Output
The node outputs an array of JSON objects representing the response from the Commanders Act API for the requested cookie. The structure depends on the API response but typically includes:
- Cookie metadata such as name, description, category, duration, and purpose.
- Configuration details relevant to cookie management and compliance.
- Any additional fields returned by the API based on query parameters.
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 node uses the base URL
https://api.commander1.com/v2. - Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
- Missing Cookie ID: If the "Cookie ID" property is not provided when required, the node throws an error indicating that the Cookie ID is required.
- API Authentication Errors: Ensure that the API key credential is correctly configured and valid; otherwise, authentication errors will occur.
- Invalid Query Parameters: Providing malformed JSON or unsupported query parameters may cause the API to reject the request.
- Network Issues: Connectivity problems can lead to request failures; verify network access to the Commanders Act API endpoint.
- Unexpected API Responses: If the API returns unexpected data formats, parsing errors might occur. Check the API documentation and ensure compatibility.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and parameters)
- n8n Documentation (for configuring credentials and using HTTP Request nodes)
This summary focuses on the "Cookie Scanner" resource and the "Get Cookie" operation as requested, based on static analysis of the provided source code and properties.