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 perform a wide range of operations on Dataiku DSS resources directly from n8n workflows. Specifically, for the Machine Learning - Lab resource and the Compute Subpopulation Analysis of Trained Model operation, the node launches the computation of subpopulation analyses for a trained machine learning model within a specified project and analysis context.
This functionality is beneficial when you want to analyze how different subpopulations (segments) behave or perform under a trained model, which can help in understanding model fairness, bias, or performance variations across groups.
Practical example:
You have a trained model deployed in Dataiku DSS and want to compute subpopulation analyses to evaluate its behavior on various customer segments (e.g., age groups, regions). Using this node, you can trigger the computation of these analyses programmatically as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Project Key | The unique identifier of the Dataiku DSS project where the model and analysis reside. |
| Analysis ID | The identifier of the specific analysis within the project related to the ML task. |
| ML Task ID | The identifier of the machine learning task associated with the trained model. |
| Model Full ID | The full identifier of the trained model for which the subpopulation analysis will be computed. |
| Request Body | A JSON object containing additional parameters or configuration for the API request. |
Output
- The output is returned as JSON data representing the response from the Dataiku DSS API after launching the subpopulation analysis computation.
- The structure typically includes details about the initiated computation task or confirmation of the action.
- If the operation involves downloading files or binary content (not applicable specifically here), the node would return binary data prepared for further use.
Dependencies
- Requires valid Dataiku DSS API credentials, including:
- The URL of the Dataiku DSS server.
- An API key for authentication.
- The node uses HTTP requests to communicate with the Dataiku DSS REST API.
- No additional external dependencies beyond the configured credentials and network access to the Dataiku DSS instance.
Troubleshooting
Missing Credentials Error:
If the node throws an error about missing credentials, ensure that the Dataiku DSS API credentials are properly configured in n8n.Required Parameter Missing:
Errors like "Project Key is required" or "Analysis ID is required" indicate that mandatory input properties were not provided. Verify all required fields are set.API Request Failures:
Network issues, incorrect URLs, or insufficient permissions may cause API call failures. Check connectivity to the Dataiku DSS server and user permissions.Invalid JSON in Request Body:
If using theRequest Bodyproperty, ensure the JSON is well-formed to avoid parsing errors.
Links and References
- Dataiku DSS API Documentation – Official API reference for Dataiku DSS.
- Subpopulation Analysis in Dataiku DSS – Explanation of subpopulation analysis concepts in Dataiku DSS.
- n8n Documentation – For general guidance on using n8n nodes and workflows.