Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API

Actions364

Overview

This node integrates with the Dataiku DSS API, enabling automation and management of various Dataiku DSS resources directly from n8n workflows. Specifically, for the "Bundles Automation-Side" resource with the "Create Project From Bundle" operation, it allows users to create a new project in Dataiku DSS based on an existing bundle. This is useful for automating project setup or deployment processes where projects are defined as bundles.

Common scenarios include:

  • Automating the creation of Dataiku projects from predefined bundles as part of CI/CD pipelines.
  • Migrating or replicating projects across different Dataiku DSS instances.
  • Integrating Dataiku project creation into broader data workflows managed by n8n.

Example: Automatically create a new Dataiku project from a bundle after uploading or receiving a bundle file, streamlining project deployment without manual intervention.

Properties

Name Meaning
Query Parameters A collection of optional key-value parameters that can be added to the API request URL query string. The available options include many flags and identifiers such as active, archivePath, deletionMode, name, etc. For this operation, relevant parameters may include those related to project creation from bundles.
data (string) Input data, typically used for file content or JSON payloads when required by the operation.
projectKey (string) The key of the project in which the bundle-related operation will be performed. Required for most operations involving projects.

The "Query Parameters" collection includes many possible options; for the "Create Project From Bundle" operation, typical parameters might include:

  • name: Name of the new project to create.
  • wait: Boolean flag indicating whether to wait for the operation to complete.
  • Other flags controlling import behavior, environment rebuild, scenario inclusion, etc.

Because the property list is extensive and shared across many operations, users should refer to the Dataiku DSS API documentation for exact parameter usage in this context.

Output

The node outputs the response from the Dataiku DSS API call:

  • If the response is JSON, it returns it as a JSON object in the json output field.
  • If the response is binary (e.g., downloading archives or files), it returns the binary data prepared for further use in n8n workflows.
  • For this specific operation ("Create Project From Bundle"), the output is expected to be JSON containing details about the created project or the status of the creation request.

Dependencies

  • Requires a valid connection to a Dataiku DSS instance.
  • Requires an API authentication token credential for Dataiku DSS (referred generically as "an API key credential").
  • The node uses HTTP requests to communicate with the Dataiku DSS REST API endpoints.
  • No additional external dependencies beyond the standard n8n environment and the provided credentials.

Troubleshooting

  • Missing Credentials Error: If the node throws an error about missing credentials, ensure that the Dataiku DSS API credentials (API key and server URL) are properly configured in n8n.
  • Required Parameter Errors: The node validates required parameters per operation. For example, "Project Key" and "Bundle ID" are mandatory for this operation. Missing these will cause errors.
  • HTTP Errors: Errors returned from the Dataiku DSS API (e.g., 4xx or 5xx responses) will be surfaced as node errors with messages including the API error details.
  • Binary Data Handling: When downloading files or archives, ensure subsequent nodes handle binary data correctly.
  • Timeouts or Long Operations: Some operations may take time; using the wait parameter controls synchronous vs asynchronous behavior.

Links and References


This summary focuses on the "Bundles Automation-Side" resource and the "Create Project From Bundle" operation, describing its purpose, input properties, output structure, dependencies, and common troubleshooting tips based on static analysis of the node's source code and provided property definitions.

Discussion