Actions364
- Continuous Activity Actions
- Dataset Actions
- Get Last Metric Values
- Get Metadata
- Get Schema
- Get Single Metric History
- List Datasets
- List Partitions
- Compute Metrics
- Create Dataset
- Create Managed Dataset
- Delete Data
- Delete Dataset
- Execute Tables Import
- Get Column Lineage
- Get Data
- Get Data - Alternative Version
- Get Dataset Settings
- Get Full Info
- List Tables
- List Tables Schemas
- Prepare Tables Import
- Run Checks
- Set Metadata
- Set Schema
- Synchronize Hive Metastore
- Update Dataset Settings
- Update From Hive Metastore
- API Service Actions
- Bundles Automation-Side Actions
- Bundles Design-Side Actions
- Connection Actions
- Dashboard Actions
- Data Collection Actions
- Data Quality Actions
- Compute Rules on Specific Partition
- Create Data Quality Rules Configuration
- Delete Rule
- Get Data Quality Project Current Status
- Get Data Quality Project Timeline
- Get Data Quality Rules Configuration
- Get Dataset Current Status
- Get Dataset Current Status per Partition
- Get Last Outcome on Specific Partition
- Get Last Rule Results
- Get Rule History
- Update Rule Configuration
- DSS Administration Actions
- Job Actions
- Library Actions
- Dataset Statistic Actions
- Discussion Actions
- Flow Documentation Actions
- Insight Actions
- Internal Metric Actions
- LLM Mesh Actions
- Machine Learning - Lab Actions
- Delete Visual Analysis
- Deploy Trained Model to Flow
- Download Model Documentation of Trained Model
- Generate Model Documentation From Custom Template
- Start Training ML Task
- Update User Metadata for Trained Model
- Update Visual Analysis
- Adjust Forecasting Parameters and Algorithm
- Compute Partial Dependencies of Trained Model
- Compute Subpopulation Analysis of Trained Model
- Create ML Task
- Create Visual Analysis
- Create Visual Analysis and ML Task
- Generate Model Documentation From Default Template
- Generate Model Documentation From File Template
- Get ML Task Settings
- Get ML Task Status
- Get Model Snippet
- Get Partial Dependencies of Trained Model
- Get Scoring Jar of Trained Model
- Get Scoring PMML of Trained Model
- Get Subpopulation Analysis of Trained Model
- Get Trained Model Details
- Get Visual Analysis
- List ML Tasks of Project
- List ML Tasks of Visual Analyses
- List Visual Analyses
- Reguess ML Task
- Machine Learning - Saved Model Actions
- Compute Partial Dependencies of Version
- Get Version Scoring PMML
- Get Version Snippet
- Import MLflow Version From File or Path
- List Saved Models
- List Versions
- Set Version Active
- Compute Subpopulation Analysis of Version
- Create Saved Model
- Delete Version
- Download Model Documentation of Version
- Evaluate MLflow Model Version
- Generate Model Documentation From Custom Template
- Generate Model Documentation From Default Template
- Generate Model Documentation From File Template
- Get MLflow Model Version Metadata
- Get Partial Dependencies of Version
- Get Saved Model
- Get Subpopulation Analysis of Version
- Get Version Details
- Get Version Scoring Jar
- Set Version User Meta
- Update Saved Model
- Long Task Actions
- Machine Learning - Experiment Tracking Actions
- Macro Actions
- Plugin Actions
- Download Plugin
- Fetch From Git Remote
- Get File Detail From Plugin
- Get Git Remote Info
- Get Plugin Settings
- Install Plugin From Git
- Install Plugin From Store
- List Files in Plugin
- List Git Branches
- List Plugin Usages
- Move File or Folder in Plugin
- Add Folder to Plugin
- Create Development Plugin
- Create Plugin Code Env
- Delete File From Plugin
- Delete Git Remote Info
- Delete Plugin
- Download File From Plugin
- Move Plugin to Dev Environment
- Pull From Git Remote
- Push to Git Remote
- Rename File or Folder in Plugin
- Reset to Local Head State
- Reset to Remote Head State
- Set Git Remote Info
- Set Plugin Settings
- Update Plugin Code Env
- Update Plugin From Git
- Update Plugin From Store
- Update Plugin From Zip Archive
- Upload File to Plugin
- Upload Plugin
- Project Deployer Actions
- Get Deployment Settings
- Get Deployment Status
- Create Deployment
- Create Infra
- Create Project
- Delete Bundle
- Delete Deployment
- Delete Infra
- Delete Project
- Get Deployment
- Get Deployment Governance Status
- Get Infra
- Get Infra Settings
- Get Project
- Get Project Settings
- Save Deployment Settings
- Save Infra Settings
- Save Project Settings
- Update Deployment
- Upload Bundle
- SQL Query Actions
- Wiki Actions
- Managed Folder Actions
- Meaning Actions
- Model Comparison Actions
- Notebook Actions
- Project Actions
- Project Folder Actions
- Recipe Actions
- Scenario Actions
- Security Actions
- Streaming Endpoint Actions
- Webapp Actions
- Workspace Actions
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 Flow Documentation resource and the operation Generate Flow Documentation From Custom Template, it allows generating flow documentation in a Dataiku project using a custom template file uploaded by the user.
Common scenarios where this node is beneficial include:
- Automating the generation of project flow documentation based on customized templates.
- Integrating Dataiku DSS documentation generation into broader automation pipelines.
- Generating consistent and repeatable documentation outputs for Dataiku projects without manual intervention.
Practical example:
- A data engineer wants to generate updated flow documentation for a Dataiku project every time a workflow completes successfully. They can use this node to trigger documentation generation using their own custom Word or HTML template, ensuring that the documentation reflects the latest project state.
Properties
| Name | Meaning |
|---|---|
| Project Key | The unique key identifying the Dataiku project for which the flow documentation will be generated. |
| File | The custom template file content (binary) to upload and use for generating the flow documentation. |
| Request Body | JSON object containing additional parameters or configuration for the API request (optional). |
Output
The node outputs the response from the Dataiku DSS API after requesting flow documentation generation. The output structure depends on the API response but generally includes:
- For successful generation requests, a JSON object confirming the initiation of the documentation generation process or providing metadata about the generated documentation.
- If the operation involves downloading generated documentation (not this specific operation), binary data representing the document file would be returned.
Since this operation triggers generation using a custom template, the output is typically JSON confirming the request status.
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Requires valid API credentials (an API key/token) for authenticating with the Dataiku DSS API.
- The node expects the Dataiku DSS server URL and user API key to be configured in the credentials.
- The custom template file must be provided as binary data attached to the node input.
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 and template file presence. Missing these will cause errors like "Project Key is required" or "File is required."
- API Request Failures: Network issues, incorrect server URLs, or invalid API keys may cause request failures. Check connectivity and credential validity.
- Invalid Template File: Uploading an unsupported or corrupted template file may cause the API to reject the request. Verify the template format and integrity.
- Unexpected Response Parsing: If the API returns non-JSON responses unexpectedly, the node attempts to handle them gracefully, but malformed responses may cause errors.
Links and References
- Dataiku DSS API Documentation - Flow Documentation
- Dataiku DSS Official Website
- n8n Documentation - Creating Custom Nodes
Note: This summary focuses exclusively on the Flow Documentation resource and the Generate Flow Documentation From Custom Template operation as requested.