Dataiku DSS

Overview

This node integrates with the Dataiku DSS API, allowing users to manage various Dataiku DSS resources programmatically within n8n workflows. Specifically for the Connection resource and the Get Connection operation, the node retrieves detailed information about a specified connection configured in the Dataiku DSS instance.

Typical use cases include:

• Automating retrieval of connection details for auditing or monitoring.
• Integrating connection metadata into broader data pipelines.
• Dynamically fetching connection configurations to use in subsequent workflow steps.

For example, you might use this node to fetch the configuration of a database connection by its name and then pass that information to another node that performs queries or data transfers using those connection details.

Properties

Note: The property is only shown for operations connectionsDelete, connectionsGet, and connectionsPut. For the Get Connection operation, this property is required to specify which connection's details to fetch.

Output

The node outputs the response from the Dataiku DSS API call as JSON data under the json field. This JSON contains the full details of the requested connection, including all its configuration parameters as defined in Dataiku DSS.

If the operation involves downloading files (not applicable for Get Connection), the node can output binary data representing the downloaded file. However, for the Get Connection operation, the output is purely JSON.

Example output structure (simplified):

{
  "connectionName": "my_connection",
  "type": "jdbc",
  "params": {
    "host": "db.example.com",
    "port": 5432,
    "database": "mydb",
    "username": "user",
    "password": "****"
  },
  "description": "Connection to production database"
}

Dependencies

• Requires an active Dataiku DSS API credential configured in n8n, providing:
  • The base URL of the Dataiku DSS server.
  • A valid user API key for authentication.
• The node makes HTTP requests to the Dataiku DSS REST API endpoints.
• No additional external dependencies are needed beyond the configured credentials.

Troubleshooting

• Missing Credentials Error: If the node throws an error about missing credentials, ensure that the Dataiku DSS API credential is properly set up in n8n with the correct server URL and API key.
• Required Parameter Errors: The node validates required parameters such as Connection Name for the Get Connection operation. Missing these will cause errors. Make sure to provide all mandatory inputs.
• HTTP Errors: If the API request fails (e.g., 404 Not Found, 401 Unauthorized), verify:
  • The connection name exists in Dataiku DSS.
  • The API key has sufficient permissions.
  • The server URL is correct and accessible.
• Parsing Errors: The node attempts to parse JSON responses. If the API returns unexpected content, it may cause parsing errors.

Links and References

• Dataiku DSS API Documentation — Official reference for available endpoints and their usage.
• Dataiku DSS Connections API — Details on managing connections via API.
• n8n Documentation — General guidance on creating and using custom nodes and credentials.