Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API
Join our community

Actions364

Overview

This node integrates with the Dataiku DSS API, allowing users to interact programmatically with various Dataiku DSS resources and operations. Specifically, for the Scenario resource and the Get Run of a Trigger operation, it retrieves detailed information about a specific run of a trigger within a scenario in a Dataiku project.

Common scenarios where this node is beneficial include:

  • Monitoring and auditing scenario executions triggered by specific events.
  • Fetching execution details for troubleshooting or reporting purposes.
  • Automating workflows that depend on the status or results of scenario trigger runs.

Practical example:

  • You have an automated data pipeline managed by Dataiku scenarios. When a trigger fires (e.g., a file arrival), you want to fetch the run details of that trigger to log or conditionally proceed with further automation steps in n8n.

Properties

Name Meaning
Project Key The unique key identifying the Dataiku project containing the scenario.
Scenario ID The identifier of the scenario from which to retrieve the trigger run information.
Trigger ID The identifier of the trigger whose run details are to be fetched.
Query Parameters Optional additional query parameters to customize the API request (key-value pairs).

Output

The output JSON contains the detailed information about the specific run of the trigger within the scenario. This includes metadata such as run status, timestamps, logs, and other relevant execution details provided by the Dataiku DSS API.

If the response is binary (not typical for this operation), it would represent downloadable content related to the scenario run, but for "Get Run of a Trigger," the output is expected to be JSON.

Example output structure (simplified):

{
  "runId": "string",
  "triggerId": "string",
  "scenarioId": "string",
  "status": "string",
  "startTime": "timestamp",
  "endTime": "timestamp",
  "logs": "string",
  "details": { /* additional run-specific details */ }
}

Dependencies

  • Requires an active connection to a Dataiku DSS instance.
  • Needs an API authentication token credential for Dataiku DSS with sufficient permissions to access scenario and trigger run information.
  • The node uses HTTP requests to the Dataiku DSS REST API endpoints.

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 like Project Key, Scenario ID, and Trigger ID. Missing any of these will cause errors. Double-check that all required fields are filled.
  • HTTP Request Failures: Network issues, incorrect server URLs, or insufficient permissions can cause API call failures. Verify connectivity and user permissions.
  • Unexpected Response Format: If the API returns unexpected data or errors, check the Dataiku DSS server logs and API documentation for changes or issues.

Links and References

This summary focuses on the Scenario resource's "Get Run of a Trigger" operation, describing its purpose, inputs, outputs, dependencies, and common troubleshooting tips based on static analysis of the provided source code and property definitions.

Discussion