Actions364
- Continuous Activity Actions
- Dataset Actions
- Get Last Metric Values
- Get Metadata
- Get Schema
- Get Single Metric History
- List Datasets
- List Partitions
- 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
- List Tables
- List Tables Schemas
- Prepare Tables Import
- Run Checks
- Set Metadata
- Set Schema
- Synchronize Hive Metastore
- Update Dataset Settings
- Update From Hive Metastore
- API Service Actions
- Bundles Automation-Side Actions
- Bundles Design-Side Actions
- Connection 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
- DSS Administration Actions
- Job Actions
- Library Actions
- Dataset Statistic Actions
- Discussion Actions
- Flow Documentation Actions
- Insight Actions
- Internal Metric Actions
- LLM Mesh Actions
- Machine Learning - Lab Actions
- Delete Visual Analysis
- Deploy Trained Model to Flow
- Download Model Documentation of Trained Model
- Generate Model Documentation From Custom Template
- Start Training ML Task
- Update User Metadata for Trained Model
- Update Visual Analysis
- Adjust Forecasting Parameters and Algorithm
- Compute Partial Dependencies of Trained Model
- Compute Subpopulation Analysis of Trained Model
- Create ML Task
- Create Visual Analysis
- Create Visual Analysis and ML Task
- Generate Model Documentation From Default Template
- Generate Model Documentation From File Template
- Get ML Task Settings
- Get ML Task Status
- Get Model Snippet
- Get Partial Dependencies of Trained Model
- Get Scoring Jar of Trained Model
- Get Scoring PMML of Trained Model
- Get Subpopulation Analysis of Trained Model
- Get Trained Model Details
- Get Visual Analysis
- List ML Tasks of Project
- List ML Tasks of Visual Analyses
- List Visual Analyses
- Reguess ML Task
- Machine Learning - Saved Model Actions
- Compute Partial Dependencies of Version
- Get Version Scoring PMML
- Get Version Snippet
- Import MLflow Version From File or Path
- List Saved Models
- List Versions
- Set Version Active
- Compute Subpopulation Analysis of Version
- Create Saved Model
- Delete Version
- Download Model Documentation of Version
- Evaluate MLflow Model Version
- Generate Model Documentation From Custom Template
- Generate Model Documentation From Default Template
- Generate Model Documentation From File Template
- Get MLflow Model Version Metadata
- Get Partial Dependencies of Version
- Get Saved Model
- Get Subpopulation Analysis of Version
- Get Version Details
- Get Version Scoring Jar
- Set Version User Meta
- Update Saved Model
- Long Task Actions
- Machine Learning - Experiment Tracking Actions
- Macro Actions
- Plugin Actions
- Download Plugin
- Fetch From Git Remote
- Get File Detail From Plugin
- Get Git Remote Info
- Get Plugin Settings
- Install Plugin From Git
- Install Plugin From Store
- List Files in Plugin
- List Git Branches
- List Plugin Usages
- Move File or Folder in Plugin
- Add Folder to Plugin
- Create Development Plugin
- Create Plugin Code Env
- Delete File From Plugin
- Delete Git Remote Info
- Delete Plugin
- Download File From Plugin
- Move Plugin to Dev Environment
- Pull From Git Remote
- Push to Git Remote
- Rename File or Folder in Plugin
- Reset to Local Head State
- Reset to Remote Head State
- Set Git Remote Info
- Set Plugin Settings
- Update Plugin Code Env
- Update Plugin From Git
- Update Plugin From Store
- Update Plugin From Zip Archive
- Upload File to Plugin
- Upload Plugin
- Project Deployer Actions
- Get Deployment Settings
- Get Deployment Status
- Create Deployment
- Create Infra
- Create Project
- Delete Bundle
- Delete Deployment
- Delete Infra
- Delete Project
- Get Deployment
- Get Deployment Governance Status
- Get Infra
- Get Infra Settings
- Get Project
- Get Project Settings
- Save Deployment Settings
- Save Infra Settings
- Save Project Settings
- Update Deployment
- Upload Bundle
- SQL Query Actions
- Wiki Actions
- Managed Folder Actions
- Meaning Actions
- Model Comparison Actions
- Notebook Actions
- Project Actions
- Project Folder Actions
- Recipe Actions
- Scenario Actions
- Security Actions
- Streaming Endpoint Actions
- Webapp Actions
- Workspace Actions
Overview
This node integrates with the Dataiku DSS API, enabling users to interact programmatically with various Dataiku DSS resources and operations. Specifically for the Data Quality resource and the Get Data Quality Project Timeline operation, it retrieves a detailed timeline of data quality statuses for each dataset within a specified project. This timeline is grouped by day and filtered between optional timestamps.
Use cases include monitoring the evolution of data quality metrics over time in a Dataiku project, auditing dataset health trends, or integrating data quality insights into automated workflows.
Example scenarios:
- Automatically fetch daily data quality status timelines to trigger alerts if quality degrades.
- Aggregate historical data quality information for reporting dashboards.
- Integrate data quality timelines into broader data governance pipelines.
Properties
| Name | Meaning |
|---|---|
| Project Key | The unique identifier of the Dataiku project for which to retrieve the data quality timeline. |
| Query Parameters | Optional additional parameters to filter or paginate the timeline data. Includes options such as: - active (boolean) - activity (string) - allUsers (boolean) - limit (number): Max number of results to return - page (number) - filter (string) - minTimestamp (number) - onlyMonitored (boolean) - resultsPerPage (number) - withScenarios (boolean) ...and many others as per the full list provided. |
The Query Parameters collection allows fine-tuning the request, such as filtering by activity, limiting results, or including/excluding certain datasets or users.
Output
The node outputs JSON data representing the detailed timeline of data quality statuses for datasets in the specified project. The structure corresponds to the response from the Dataiku DSS API endpoint /projects/{projectKey}/data-quality/timeline.
- The output JSON typically includes entries grouped by date, each containing data quality status details per dataset.
- If the operation involves downloading files or binary content (not applicable here), the node would output binary data accordingly.
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Needs valid API credentials consisting of 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" for authentication.
- The node makes HTTP requests to the Dataiku DSS REST API endpoints.
Troubleshooting
- Missing Credentials Error: If the node throws "Missing Dataiku DSS API Credentials," ensure that the API key credential is properly set up in n8n.
- Required Parameter Errors: The node validates required parameters like
Project Key. Missing these will cause errors such as "Project Key is required." - HTTP Request Failures: Network issues, incorrect server URLs, or invalid API keys can cause request failures. Verify connectivity and credentials.
- Unexpected Response Format: If the API changes or returns unexpected data, parsing errors may occur. Check the Dataiku DSS API version compatibility.
- Large Result Sets: When requesting large timelines, consider using pagination parameters (
limit,page) to avoid timeouts or memory issues.
Links and References
- Dataiku DSS API Documentation
- Dataiku DSS Data Quality API Reference
- n8n Documentation on HTTP Request Node
This summary focuses on the Data Quality resource's Get Data Quality Project Timeline operation, describing its purpose, inputs, outputs, dependencies, and common troubleshooting tips based on static analysis of the provided source code and property definitions.