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
The "Update Cookie" operation in the Commanders Act node allows users to update an existing cookie's information within the Commanders Act Cookie Scanner service. This operation is useful for managing and maintaining accurate cookie data, such as modifying cookie attributes or metadata after creation.
Typical scenarios include:
- Updating cookie details when privacy policies change.
- Correcting or enriching cookie descriptions or classifications.
- Managing cookies dynamically based on website changes or compliance requirements.
For example, a user might update the purpose or expiration date of a cookie to ensure that the cookie scanner reflects the current state of cookies used on their website.
Properties
| Name | Meaning |
|---|---|
| Cookie ID | The unique identifier of the cookie to update. |
| Query Parameters | Optional parameters to customize the API request, including filters, pagination, sorting, etc. (various options available). |
| Request Body | JSON object containing the updated cookie data to be sent in the request body. |
Details on Query Parameters Options (selected examples):
- End: End date/time filter.
- Fields[template]: Template fields selection.
- Filter: JSON filter criteria.
- Granularity: Data granularity level.
- Include: Additional related data to include.
- Page: Pagination settings.
- Sort: Sorting criteria.
- Token: An optional token for authentication or session management.
Output
The output is a JSON array where each element corresponds to the response from the API call for each input item processed.
- The
jsonfield contains the parsed JSON response from the Commanders Act API representing the updated cookie resource. - If the API returns no content (HTTP 204), the output will contain a status code message indicating "204 No Content".
- The node does not output binary data.
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. - Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
- Missing Cookie ID: The operation requires a valid Cookie ID; if omitted, the node throws an error "Cookie ID is required".
- Invalid JSON in Request Body: The request body must be valid JSON; malformed JSON will cause errors.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network or API Errors: The node wraps API errors and provides messages like "Error calling Commanders Act API" with details; check network connectivity and API status.
- Unexpected Response Format: If the API returns a non-JSON string, the node attempts to parse it; failure results in returning raw text.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes