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 to manage Data Cleansing Transformations, specifically supporting operations such as updating existing cleansing transformations. It allows users to modify cleansing transformation configurations programmatically within an n8n workflow.
Typical use cases include automating updates to data cleansing rules or transformations that are applied to datasets before further processing or analysis. For example, a user might update a cleansing transformation to adjust how certain data fields are normalized or filtered based on evolving business requirements.
Properties
| Name | Meaning |
|---|---|
| Cleansing Transformation ID | The unique identifier of the cleansing transformation to update. Required for update operations. |
| Query Parameters | Optional parameters to customize the API request, such as filters, pagination, sorting, etc. |
| Request Body | JSON object containing the data to update the cleansing transformation with. |
The Query Parameters collection supports various optional parameters like end, filter, granularity, include, page, sort, source, start, and token (an API token), allowing fine control over the request context.
Output
The node outputs the JSON response from the Commanders Act API after performing the update operation. The output structure corresponds directly to the API's response for the updated cleansing transformation, typically including details of the updated resource.
If the API returns a string response, the node attempts to parse it as JSON; if parsing fails, 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 produced by this node.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires valid API credentials (an API key/token and site ID) configured in n8n.
- The base URL used for API requests is
https://api.commander1.com/v2. - The node uses standard HTTP methods (PATCH for update) and expects JSON content type.
Troubleshooting
- Missing Credentials Error: If API credentials are not set or invalid, the node throws an error "Missing Commanders Act API Credentials". Ensure credentials are properly configured.
- Required Parameter Missing: For update operations, the "Cleansing Transformation ID" must be provided. Omitting it results in an error indicating the missing ID.
- API Errors: Any errors returned by the API are wrapped and rethrown as node errors with messages prefixed by "Error calling Commanders Act API". Check the API response and ensure request body and parameters are correct.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON will cause parsing errors.
- Network Issues: Connectivity problems to the API endpoint will cause request failures.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes