Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Web Container Actions
- Get Web Tag
- 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 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
- 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 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
Data Cleansing → Store Cleansing Transformations
AI-generatedOverview
This node interacts with the Commanders Act API to manage data cleansing transformations, specifically to store cleansing transformations. It is useful for scenarios where users need to automate the storage of data cleansing rules or transformations within the Commanders Act platform, enabling streamlined data quality management and integration workflows.
Use Case Examples
- Automatically store new data cleansing transformations based on input data.
- Integrate with Commanders Act to update cleansing transformations as part of a data pipeline.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional query parameters to customize the API request, such as filtering, pagination, sorting, and other parameters relevant to the data cleansing transformations storage operation. |
| Request Body | JSON object representing the data cleansing transformation to be stored. |
Output
JSON
json- The JSON response from the Commanders Act API representing the result of the store cleansing transformation operation.
Dependencies
- Commanders Act API with API token credentials
Troubleshooting
- Ensure that the API credentials (site ID and API token) are correctly configured and provided; missing credentials will cause an error.
- Verify that the required parameters such as the cleansing transformation ID (if applicable) are provided; missing required IDs will cause an error.
- Check the format of the request body JSON to ensure it is valid; invalid JSON will cause the API request to fail.
- Review the API endpoint URL construction for correctness, especially the site ID and query parameters.
- Common error messages include missing required parameters or authentication failures; resolving these involves providing the correct parameters and valid credentials.