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 to perform various operations on Dataiku DSS resources. Specifically, for the Discussion resource and the Reply Discussion operation, it allows users to post a reply to an existing discussion within a specified project and object context.
Typical use cases include:
- Automating responses to discussions related to projects or datasets.
- Integrating discussion replies into workflows that monitor or manage project activities.
- Enabling programmatic interaction with Dataiku DSS discussions for collaboration or audit purposes.
Example: Replying to a discussion thread about a dataset issue automatically when certain conditions are met in a data pipeline.
Properties
| Name | Meaning |
|---|---|
| Project Key | The key identifier of the Dataiku DSS project where the discussion exists. |
| Object Type | The type/category of the object (e.g., dataset, recipe) to which the discussion belongs. |
| Object ID | The unique identifier of the specific object instance related to the discussion. |
| Discussion ID | The unique identifier of the discussion thread to which the reply will be posted. |
| Request Body | JSON object containing the content of the reply message and any additional parameters. |
Output
The node outputs the response from the Dataiku DSS API after posting the reply. The output is structured as JSON and typically contains details about the newly created reply, such as its ID, timestamp, author, and content.
If the API returns binary data (not typical for this operation), it would be provided as binary output, but for replying to discussions, the output is JSON.
Dependencies
- Requires valid Dataiku DSS API credentials including:
- The DSS server URL.
- A user API key for authentication.
- The node must be configured with these credentials in n8n before execution.
Troubleshooting
- Missing Credentials Error: If the node throws "Missing Dataiku DSS API Credentials," ensure that the API credentials are properly set up in n8n.
- Required Parameter Errors: The node validates required parameters like Project Key, Object Type, Object ID, and Discussion ID. Missing any of these will cause errors. Double-check that all required fields are filled.
- API Errors: Errors returned by the Dataiku DSS API will be wrapped and shown with messages like "Error calling Dataiku DSS API." Check the error message and stack trace for details.
- Invalid JSON in Request Body: Ensure the JSON provided in the Request Body property is well-formed.
Links and References
- Dataiku DSS API Documentation
- Dataiku DSS Discussions API Reference
- n8n Documentation on HTTP Request Node
This summary focuses on the Discussion resource and the Reply Discussion operation as requested.