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 interacts with the Dataiku DSS API to perform various operations on datasets within a Dataiku project. Specifically, for the "Dataset" resource and the "Delete Dataset" operation, it allows users to delete an entire dataset from a specified project in Dataiku DSS.
Common scenarios where this node is beneficial include:
- Automating the cleanup of datasets that are no longer needed.
- Managing datasets programmatically as part of a larger data pipeline or workflow.
- Integrating dataset deletion into CI/CD pipelines or scheduled automation tasks.
Example use case:
- A user wants to delete a dataset named "sales_data_2023" from the project "RetailProject" after archiving its contents elsewhere. This node can be configured to perform that deletion automatically.
Properties
| Name | Meaning |
|---|---|
| Project Key | The unique identifier (key) of the Dataiku project containing the dataset. |
| Dataset Name | The name of the dataset to delete within the specified project. |
| Query Parameters | Optional additional parameters as key-value pairs to customize the API request. |
Output
The output of the node is a JSON array containing the response from the Dataiku DSS API after attempting to delete the dataset. The structure depends on the API's response but typically includes confirmation of deletion or error details.
If the deletion is successful, the output may be empty or contain status information. If there is an error, the output will include error messages describing the failure.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Requires valid API credentials: specifically, a server URL and a user API key for authentication.
- The node expects the Dataiku DSS API to be accessible at the provided server address.
- No additional external services are required beyond the Dataiku DSS API.
Troubleshooting
- Missing Credentials: The node will throw an error if the API credentials (server URL and API key) are not provided or invalid.
- Missing Required Parameters: Errors occur if the "Project Key" or "Dataset Name" is not specified when performing the delete operation.
- API Errors: If the dataset does not exist or the user lacks permissions, the API will return an error which the node surfaces. Check that the project and dataset names are correct and that the API key has sufficient privileges.
- Network Issues: Connectivity problems to the Dataiku DSS server will cause request failures.
- Unexpected Response Format: If the API returns unexpected data, parsing errors might occur; ensure the API version matches expectations.
To resolve common errors:
- Verify all required input fields are filled correctly.
- Confirm API credentials are valid and have necessary permissions.
- Ensure the Dataiku DSS server is reachable from the n8n environment.
- Review API documentation for any changes in endpoint behavior.