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
This node integrates with the Commanders Act API, specifically enabling management of various resources including the Cookie Scanner. The "Create Custom Field" operation under the Cookie Scanner resource allows users to create new custom fields for cookies within the Commanders Act platform. This is useful for organizations that want to extend cookie metadata with additional custom attributes tailored to their compliance or reporting needs.
Typical use cases include:
- Adding new descriptive or classification fields to cookies scanned on a website.
- Enhancing cookie data for better consent management and reporting.
- Automating the creation of custom fields as part of a broader data governance workflow.
Example: Automatically creating a custom field named "Data Sensitivity" to classify cookies by sensitivity level.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional URL query parameters to customize the API request. Includes options like end, filter, page, sort, token (API token), etc. These allow filtering, pagination, sorting, and authentication details. |
| Request Body | JSON object representing the body of the POST request to create the custom field. This should contain the details of the custom field to be created, such as its name, type, description, and other relevant attributes. |
The Query Parameters property supports multiple optional parameters such as:
end,start: Date/time range filters.filterand nested filter options for advanced querying.page: Pagination controls.sort: Sorting instructions.token: An API token for authentication (password type).
Output
The node outputs the JSON response from the Commanders Act API after attempting to create the custom field. The output structure corresponds directly to the API's response schema for the custom field creation endpoint, typically including details of the newly created custom field such as its ID, name, type, and any other metadata returned by the API.
If the API returns no content (HTTP 204), the node outputs an object indicating "Status Code": "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires valid API credentials (an API key/token) configured in n8n.
- The base URL used is
https://api.commander1.com/v2. - The node uses HTTP methods POST with JSON payloads for creating custom fields.
Troubleshooting
- Missing Credentials: If API credentials are not provided or invalid, the node will throw an error indicating missing credentials.
- Required Parameters Missing: The node checks for required IDs or parameters depending on the operation. For creating a custom field, ensure the request body is properly defined.
- 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 and permissions.
- Ensure all required input properties are set correctly.
- Validate JSON syntax in the request body.
- Check network connectivity and API availability.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and payloads)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.