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 manage a wide range of Dataiku DSS resources and operations programmatically within n8n workflows. It supports numerous resources such as meanings, connections, dashboards, datasets, machine learning models, scenarios, plugins, and many more.
For the Meaning resource with the Create Meaning operation, this node allows creating new "meaning" entities in Dataiku DSS. Meanings in Dataiku DSS are user-defined semantic labels or metadata that can be applied to data columns or datasets to provide additional context or interpretation.
Common scenarios:
- Automating the creation of semantic metadata (meanings) for datasets during data pipeline execution.
- Integrating Dataiku DSS meaning management into larger automated workflows.
- Programmatically updating or managing meanings as part of data governance or cataloging processes.
Practical example:
- A workflow that creates a new meaning describing a specific business concept (e.g., "Customer Age Group") by sending a JSON definition to the Dataiku DSS API via this node.
Properties
| Name | Meaning |
|---|---|
| Request Body | JSON object containing the details of the meaning to create. This should follow the Dataiku DSS API schema for meanings. |
The Request Body property is used to specify the full JSON payload sent to the API when creating a meaning. It must contain all necessary fields as required by the Dataiku DSS API for the meanings resource.
Output
The node outputs the response from the Dataiku DSS API call in the json field of the output item. For the "Create Meaning" operation, this typically includes the newly created meaning object returned by the API, which contains details such as the meaning ID, name, description, and other metadata.
If the API returns binary data (not typical for this operation), it would be provided in the binary field, but for creating meanings, the output is JSON.
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Requires valid API credentials (an API key token) for authenticating requests to the Dataiku DSS API.
- The node expects the Dataiku DSS server URL and user API key to be configured in the credentials.
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 like
meaningIdfor update/get operations or project keys for project-scoped resources. Missing these will cause errors. - Invalid JSON in Request Body: Ensure the JSON provided in the
Request Bodyproperty is well-formed and matches the expected schema for meanings. - API Errors: Errors returned from the Dataiku DSS API will be surfaced with messages indicating the problem (e.g., permission denied, invalid data). Check the API documentation and your permissions.
- Network Issues: Verify connectivity to the Dataiku DSS server and that the server URL is correct.
Links and References
- Dataiku DSS API Documentation - Meanings (official API docs for meanings)
- Dataiku DSS Concepts - Meanings (conceptual overview of meanings in Dataiku DSS)
This summary focuses on the "Meaning" resource and the "Create Meaning" operation as requested, based on static analysis of the provided source code and input properties.