Actions83
- 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
Overview
The "Update Custom Field" operation in the Commanders Act node allows users to update an existing custom field within the Cookie Scanner resource. This operation is useful for managing and modifying metadata or attributes related to cookies scanned on a website, enabling better customization and control over cookie data.
Typical use cases include:
- Modifying the properties of a cookie custom field to reflect changes in compliance requirements.
- Updating descriptions or settings of custom fields used in cookie scanning reports.
- Automating updates to cookie metadata as part of a broader data governance workflow.
For example, if a company needs to change the label or parameters of a cookie attribute tracked by their cookie scanner, this operation can be used to programmatically apply those changes via the API.
Properties
| Name | Meaning |
|---|---|
| Custom Field ID | The unique identifier of the custom field to update. |
| Query Parameters | Optional additional query parameters to customize the API request. |
| Request Body | JSON object containing the fields and values to update in the custom field. |
Details on Properties:
- Custom Field ID: Required to specify which custom field will be updated.
- Query Parameters: A collection of optional parameters such as filters, pagination, sorting, date ranges, etc., that can be appended to the API request URL.
- Request Body: A JSON structure representing the new values or changes to apply to the custom field. This must be provided when performing the update.
Output
The output of this operation is the JSON response returned by the Commanders Act API after updating the custom field. It typically contains the updated custom field's details, confirming the changes applied.
If the API returns a string response, the node attempts to parse it as JSON; otherwise, it outputs the raw text. If no content is returned (HTTP 204), the node outputs a status message indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires valid API credentials including a site identifier and an API token.
- The node expects these credentials to be configured in n8n prior to execution.
Troubleshooting
- Missing Custom Field ID: The node throws an error if the Custom Field ID is not provided, as it is mandatory to identify which custom field to update.
- Invalid JSON in Request Body: Ensure the JSON provided in the Request Body is well-formed; otherwise, the node will fail parsing it.
- API Authentication Errors: If credentials are missing or invalid, the node will throw an authentication error.
- Unknown Resource or Operation: Using unsupported resource or operation names will cause errors.
- Network or API Errors: Any issues with connectivity or API availability will result in errors with messages from the API.
To resolve errors:
- Verify all required parameters are set.
- Check API credentials and permissions.
- Validate JSON syntax in the request body.
- Review API documentation for correct endpoint usage.
Links and References
- Commanders Act API Documentation (official API base URL)
- Refer to Commanders Act platform documentation for detailed schema of custom fields and update operations.