Actions364
- API Service Actions
- Bundles Automation-Side Actions
- Bundles Design-Side Actions
- Connection Actions
- Continuous Activity 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
- Dataset Actions
- 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
- Get Last Metric Values
- Get Metadata
- Get Schema
- Get Single Metric History
- List Datasets
- List Partitions
- List Tables
- List Tables Schemas
- Prepare Tables Import
- Run Checks
- Set Metadata
- Set Schema
- Synchronize Hive Metastore
- Update Dataset Settings
- Update From Hive Metastore
- Dataset Statistic Actions
- Discussion Actions
- DSS Administration Actions
- Flow Documentation Actions
- Insight Actions
- Internal Metric Actions
- Job Actions
- Library Actions
- LLM Mesh Actions
- Long Task Actions
- Machine Learning - Experiment Tracking Actions
- Machine Learning - Lab Actions
- 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
- Delete Visual Analysis
- Deploy Trained Model to Flow
- Download Model Documentation of Trained Model
- Generate Model Documentation From Custom Template
- 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
- Start Training ML Task
- Update User Metadata for Trained Model
- Update Visual Analysis
- Machine Learning - Saved Model Actions
- Compute Partial Dependencies of Version
- 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
- Get Version Scoring PMML
- Get Version Snippet
- Import MLflow Version From File or Path
- List Saved Models
- List Versions
- Set Version Active
- Set Version User Meta
- Update Saved Model
- Macro Actions
- Managed Folder Actions
- Meaning Actions
- Model Comparison Actions
- Notebook Actions
- Plugin Actions
- 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
- 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
- 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 Actions
- Project Deployer Actions
- Create Deployment
- Create Infra
- Create Project
- Delete Bundle
- Delete Deployment
- Delete Infra
- Delete Project
- Get Deployment
- Get Deployment Governance Status
- Get Deployment Settings
- Get Deployment Status
- Get Infra
- Get Infra Settings
- Get Project
- Get Project Settings
- Save Deployment Settings
- Save Infra Settings
- Save Project Settings
- Update Deployment
- Upload Bundle
- Project Folder Actions
- Recipe Actions
- Scenario Actions
- Security Actions
- SQL Query Actions
- Streaming Endpoint Actions
- Webapp Actions
- Wiki Actions
- Workspace Actions
Plugin → Rename File or Folder in Plugin
AI-generatedOverview
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 "Plugin" resource and the "Rename File or Folder in Plugin" operation, it allows renaming files or folders within a specified plugin.
Common scenarios where this node is beneficial include automating plugin management tasks such as updating plugin contents, managing plugin files and folders, and integrating plugin lifecycle actions into broader automation workflows. For example, a user might automate the renaming of plugin files after deployment or during development cycles without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Plugin ID | The unique identifier of the plugin where the file or folder rename operation will occur. |
| Request Body | A JSON object containing the details of the rename operation, typically specifying the current name/path and the new name/path for the file or folder. |
Note: The "Request Body" property expects a JSON structure that defines the rename parameters according to the Dataiku DSS API specification for plugin content rename actions.
Output
The node outputs the response from the Dataiku DSS API call:
- JSON output: Contains the parsed JSON response from the API if the response is JSON.
- Binary output: Not applicable for this operation.
- If the API returns no content (HTTP 204), the output will indicate
"Status Code": "204 No Content".
The output reflects the result of the rename operation, which may include success confirmation or error details.
Dependencies
- Requires an active connection to a Dataiku DSS instance.
- Requires valid API credentials (an API key) for authentication with the Dataiku DSS API.
- The node uses HTTP requests to communicate with the Dataiku DSS server; thus, network connectivity to the server is necessary.
- No additional external services are required beyond the Dataiku DSS API.
Troubleshooting
- Missing Credentials Error: If the node throws an error about missing credentials, ensure that the API key credential for Dataiku DSS is properly configured in n8n.
- Required Parameter Errors: The node validates required parameters such as Plugin ID and request body fields. Missing these will cause errors. Verify all required inputs are provided.
- API Endpoint Errors: If the plugin ID is incorrect or the file/folder paths in the request body do not exist, the API may return errors. Confirm the plugin and paths are correct.
- Network Issues: Connectivity problems to the Dataiku DSS server will cause request failures. Check network access and server availability.
- Unexpected Response Format: If the API returns non-JSON responses unexpectedly, the node attempts to handle them gracefully but may output raw text.
Links and References
- Dataiku DSS API Documentation – Official API reference for understanding request bodies and endpoints.
- Dataiku DSS Plugins Documentation – Information on managing plugins and their contents.
- n8n Documentation – For general guidance on using n8n nodes and credentials.
This summary focuses on the "Plugin" resource and the "Rename File or Folder in Plugin" operation, describing how the node constructs the API request, handles inputs, and processes outputs accordingly.