Actions16
Overview
This node interacts with the Hypris API to manage various resources such as databases, items, views, properties, resource items, and workspaces. Specifically, for the View - Update operation, it allows users to rename an existing view within a specified database. This is useful when you want to programmatically update the name of a view in your Hypris workspace without manually changing it through the UI.
Common scenarios:
- Renaming views to reflect updated project requirements or naming conventions.
- Automating maintenance tasks where views need to be renamed based on external triggers or workflows.
- Integrating Hypris view management into larger automation pipelines.
Example:
You have a view named "Q1 Sales" in a database and want to rename it to "Q1 Sales Updated" automatically after importing new data.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | The workspace containing the database and view. Choose from a list or specify an ID via expression. |
| Database Name or ID | The database that contains the view to update. Choose from a list or specify an ID via expression. |
| View Name or ID | The specific view to update. Choose from a list or specify an ID via expression. |
| New View Name | The new name to assign to the selected view. |
Output
The node outputs JSON data representing the updated view object returned by the Hypris API after renaming. The structure typically includes details about the view such as its ID, new name, type, and other metadata as provided by the API response.
If multiple input items are processed, the output will be an array of JSON objects corresponding to each updated view.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Hypris API using valid credentials (an API key or username/password).
- The node depends on the Hypris API endpoints for workspaces, databases, and views.
- Proper configuration of the Hypris API credentials in n8n is necessary.
- Network access to the Hypris API base URL must be available.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Specifying incorrect workspace, database, or view IDs may result in "not found" errors.
- Network connectivity problems can lead to request timeouts or failures.
- Insufficient permissions on the API user may prevent updating views.
Error messages and resolutions:
"Failed to load views": Check if the database ID is correct and accessible."Authentication failed": Verify API credentials and re-enter them if needed."View not found": Confirm the view ID exists in the specified database."Request timeout": Ensure network connectivity and retry the operation.
Links and References
- Hypris API Documentation (hypothetical link as no direct link provided)
- n8n Expressions Documentation
- n8n Credential Management
This summary is based solely on static analysis of the provided source code and property definitions.