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, allowing users to manage various aspects of their Dataiku DSS projects programmatically within n8n workflows. Specifically, for the API Service resource and the Publish Package operation, it enables publishing an API service package to the API Deployer.
Typical use cases include automating deployment pipelines where after generating or updating an API service package in Dataiku DSS, you want to publish it automatically without manual intervention. This is useful in continuous integration/continuous deployment (CI/CD) scenarios, ensuring that the latest API packages are deployed promptly.
Example: After a successful model training and packaging step in Dataiku DSS, this node can be used to publish the new API package so that it becomes available for consumption by other applications or services.
Properties
| Name | Meaning |
|---|---|
| Project Key | The unique key identifying the Dataiku DSS project containing the API service. |
| Service ID | The identifier of the API service within the project. |
| Package ID | The identifier of the specific package of the API service to publish. |
| Query Parameters | Optional additional query parameters to customize the publish request. |
Output
The node outputs the response from the Dataiku DSS API call in JSON format under the json field. The output typically contains details about the published package or confirmation of the publish action.
If the operation involves downloading files or binary data (not applicable for Publish Package), the node would output binary data accordingly, but for publishing, the output is JSON.
Dependencies
- Requires valid Dataiku DSS API credentials including:
- The DSS server URL.
- A user API key for authentication.
- The node uses HTTP requests to communicate with the Dataiku DSS REST API.
- No additional external dependencies beyond the configured API credentials.
Troubleshooting
- Missing Credentials Error: If the node throws "Missing Dataiku DSS API Credentials," ensure that the API key credential is properly configured in n8n.
- Required Parameter Errors: The node validates required parameters such as Project Key, Service ID, and Package ID. Missing any of these will cause errors like "Project Key is required." Make sure all required fields are filled.
- HTTP Errors: Errors returned from the Dataiku DSS API (e.g., 4xx or 5xx status codes) will be surfaced as node errors with messages prefixed by "Error calling Dataiku DSS API." Check the API server logs or network connectivity if these occur.
- Invalid JSON Response: If the API returns non-JSON or unexpected responses, the node attempts to parse them; failure results in raw text output. Verify the API endpoint and parameters.
Links and References
- Dataiku DSS API Documentation
- Dataiku DSS API Services Guide
- n8n Documentation on Creating Custom Nodes
This summary focuses on the API Service resource and the Publish Package operation as requested, based on static analysis of the provided source code and property definitions.