Dataiku DSSInstall

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 From Trigger Run operation, it retrieves the run of a scenario that was initiated by a specific trigger run. This is useful in automation workflows where you want to track or analyze the execution of scenarios triggered by other runs.

Common use cases include:

• Monitoring scenario executions triggered by specific events.
• Fetching detailed information about scenario runs linked to trigger runs for auditing or reporting.
• Automating follow-up actions based on the outcome of triggered scenario runs.

Example: You have a trigger run ID from an event and want to get the corresponding scenario run details to check its status or logs.

Properties

The Query Parameters collection supports multiple optional parameters such as active, limit, page, etc., which can be used to refine the API call.

Output

The node outputs JSON data representing the scenario run associated with the given trigger run. The structure corresponds to the Dataiku DSS API response for scenario runs, typically including details like run ID, status, start/end times, steps executed, and any output or error messages.

If the operation involves downloading files or binary content (not applicable specifically for this operation), the node would output binary data prepared accordingly.

Dependencies

• Requires an active connection to a Dataiku DSS instance.
• Needs valid API credentials (an API key) for authentication.
• The node uses HTTP requests to communicate with the Dataiku DSS REST API.
• No additional external dependencies beyond standard n8n helpers and the Dataiku DSS API.

Troubleshooting

• Missing Credentials Error: If the API key credential is not set or invalid, the node will throw an error indicating missing credentials.
• Required Parameter Missing: The node validates required parameters like Project Key and Scenario ID; missing these will cause errors.
• API Request Failures: Network issues, incorrect URLs, or insufficient permissions may cause API call failures. Check the Dataiku DSS server URL and API key permissions.
• Parsing Errors: If the API returns unexpected data formats, JSON parsing might fail. Ensure the API version and endpoint are correct.
• Trigger Run ID Not Found: If the specified trigger run ID does not correspond to any scenario run, the API may return empty or error responses.

To resolve errors:

• Verify all required input fields are correctly filled.
• Confirm API credentials and permissions.
• Check network connectivity to the Dataiku DSS server.
• Review API documentation for any changes in endpoints or parameters.

Links and References

• Dataiku DSS API Documentation
• Scenario Runs API Reference
• n8n HTTP Request Node Documentation

This summary focuses on the Scenario resource's "Get Run From Trigger Run" operation within the Dataiku DSS node, describing its purpose, inputs, outputs, and usage context based on static code analysis.