Actions16
Overview
This node interacts with the Hypris API to manage workspaces and other related resources. Specifically, the Workspace - Rename operation allows users to rename an existing workspace by specifying its current name or ID and providing a new name. This is useful for organizing or updating workspace titles without recreating them.
Common scenarios:
- Renaming a workspace to reflect a change in project scope or team structure.
- Correcting typos or standardizing workspace names.
- Automating workspace management workflows where names need to be updated dynamically.
Practical example:
You have a workspace named "Project Alpha" but want to rename it to "Project Alpha - Phase 2". Using this node, you select the workspace and provide the new name, automating the update via the Hypris API.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | The workspace to rename. Choose from the list of available workspaces or specify an ID using an expression. |
| New Workspace Name | The new name to assign to the selected workspace. |
Output
The node outputs JSON data representing the result of the rename operation. Typically, this will include details about the renamed workspace such as its updated name and possibly other metadata returned by the Hypris API.
If multiple input items are processed, the output will be an array of JSON objects corresponding to each rename operation's result.
The node does not output binary data.
Dependencies
- Requires an active connection to the Hypris API.
- Needs an API authentication credential (username and password) configured in n8n to authorize requests.
- The node uses HTTP Basic Authentication to communicate with the Hypris API endpoints.
- The
workspaceIdproperty options are dynamically loaded from the Hypris API based on the authenticated user’s accessible workspaces.
Troubleshooting
Common issues:
- Invalid or missing workspace ID/name: Ensure the workspace exists and the correct identifier is used.
- Authentication failures: Verify that the API credentials are correctly set up and have sufficient permissions.
- Network or API endpoint errors: Check connectivity and the base URL configuration.
Error messages:
- Errors during loading workspace options or executing the rename request typically include HTTP error details.
- If the node throws an error about failing to load workspaces, check API credentials and network access.
- If renaming fails, the error message usually indicates whether the workspace was not found or if the new name is invalid.
Resolution tips:
- Use expressions carefully when specifying workspace IDs.
- Confirm that the new workspace name meets any naming constraints imposed by the Hypris API.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in batch operations.
Links and References
- Hypris API Documentation (hypothetical link as no direct link provided)
- n8n Expressions Documentation
- n8n Credential Setup