Actions100
- API Service Actions
- Bundles Automation-Side Actions
- Bundles Design-Side Actions
- Connection Actions
- Continuous Activity Actions
- Dashboard Actions
- Data Collection Actions
- Data Quality Actions
- Compute Rules on Specific Partition
- Create Data Quality Rules Configuration
- Delete Rule
- Get Data Quality Project Current Status
- Get Data Quality Project Timeline
- Get Data Quality Rules Configuration
- Get Dataset Current Status
- Get Dataset Current Status per Partition
- Get Last Outcome on Specific Partition
- Get Last Rule Results
- Get Rule History
- Update Rule Configuration
- Dataset Actions
- Compute Metrics
- Create Dataset
- Create Managed Dataset
- Delete Data
- Delete Dataset
- Execute Tables Import
- Get Column Lineage
- Get Data
- Get Data - Alternative Version
- Get Dataset Settings
- Get Full Info
- Get Last Metric Values
- Get Metadata
- Get Schema
- Get Single Metric History
- List Datasets
- List Partitions
- List Tables
- List Tables Schemas
- Prepare Tables Import
- Run Checks
- Set Metadata
- Set Schema
- Synchronize Hive Metastore
- Update Dataset Settings
- Update From Hive Metastore
- Dataset Statistic Actions
- Discussion Actions
- DSS Administration Actions
Overview
This node integrates with the Dataiku DSS API, allowing users to perform a wide range of operations on Dataiku DSS resources. Specifically for the Data Quality resource and the Update Rule Configuration operation, it enables updating the configuration of a specific data quality rule on a dataset within a project.
Common scenarios where this node is beneficial include:
- Automating updates to data quality rules as part of a data pipeline.
- Managing data quality configurations programmatically without manual intervention in the Dataiku DSS UI.
- Integrating data quality rule updates into broader workflows that involve dataset management or monitoring.
For example, you might use this node to update thresholds or parameters of a data quality rule after analyzing recent data trends, ensuring your data validation remains accurate and relevant.
Properties
Name | Meaning |
---|---|
Project Key | The unique identifier of the Dataiku DSS project containing the dataset. |
Dataset Name | The name of the dataset on which the data quality rule is configured. |
Rule ID | The identifier of the specific data quality rule to update. |
Request Body | A JSON object representing the new configuration settings for the data quality rule. |
Output
The node outputs the response from the Dataiku DSS API after attempting to update the rule configuration. The output is structured as JSON and typically contains details about the updated rule configuration or confirmation of the update.
If the API returns binary data (not typical for this operation), it would be provided as binary output, but for the Update Rule Configuration operation, the output is JSON.
Example output structure (simplified):
{
"ruleId": "string",
"status": "updated",
"configuration": {
// Updated rule configuration details
}
}
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Needs valid API credentials including the DSS server URL and a user API key.
- The node expects these credentials to be configured in n8n under a generic API key credential type (referred generically as "an API key credential").
- The Dataiku DSS API must be accessible from the environment where n8n runs.
Troubleshooting
- Missing Credentials Error: If the node throws an error about missing credentials, ensure that the Dataiku DSS API credentials are properly set up in n8n.
- Required Parameter Errors: The node validates required parameters such as Project Key, Dataset Name, and Rule ID. Missing any of these will cause an error. Double-check that all required fields are filled.
- API Request Failures: Network issues, incorrect API keys, or insufficient permissions can cause API call failures. Verify network connectivity, API key validity, and user permissions in Dataiku DSS.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON syntax will cause errors. Use proper JSON formatting.
- Unexpected Response Format: If the API response cannot be parsed as JSON, the node attempts to return raw text. This may indicate an issue with the API or the request.
Links and References
- Dataiku DSS API Documentation
- Dataiku DSS Data Quality Rules
- n8n Documentation - Creating Custom Nodes
This summary focuses on the Data Quality resource and the Update Rule Configuration operation as requested, based on static analysis of the provided source code and property definitions.