Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API

Actions364

Overview

This node integrates with the Dataiku DSS API, enabling users to perform a wide range of operations on Dataiku DSS resources directly from n8n workflows. Specifically, for the API Service resource and the Download Package Archive operation, the node downloads a package archive associated with an API service within a specified project.

Typical use cases include automating the retrieval of API service packages for backup, deployment, or further processing. For example, a user might automate downloading the latest version of an API service package archive after it is generated, to store it externally or deploy it elsewhere.

Properties

Name Meaning
Project Key The key identifier of the Dataiku project containing the API service.
Service ID The identifier of the API service whose package archive is to be downloaded.
Package ID The identifier of the specific package within the API service to download the archive for.

Output

The output contains the downloaded package archive as binary data under the binary.data field. This binary data represents the zipped package archive file (service_package.zip) of the specified API service package.

If the operation succeeds, the node returns one item with the binary content ready for further use in the workflow (e.g., saving to disk, uploading elsewhere).

Dependencies

  • Requires valid Dataiku DSS API credentials including:
    • The DSS server URL.
    • A user API key for authentication.
  • The node expects these credentials to be configured in n8n prior to execution.
  • The node makes HTTP requests to the Dataiku DSS REST API endpoints.

Troubleshooting

  • Missing Credentials Error: If the node throws "Missing Dataiku DSS API Credentials", ensure that the API key credential is properly set up 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". Provide all mandatory inputs.
  • HTTP Request Failures: Network issues or incorrect server URLs can cause request failures. Verify connectivity and correct server address.
  • Invalid Package or Service IDs: Using non-existent Service ID or Package ID will result in API errors. Confirm IDs are correct.
  • Binary Data Handling: Ensure downstream nodes can handle binary data if you intend to process or save the downloaded archive.

Links and References

Discussion