Actions36
- Automation Actions
- Execution Actions
- Notification Actions
- Platform Actions
- Prompt Actions
- Proxy Actions
- Result Actions
- Run Automation Actions
- Social Account Actions
- Workflow Actions
- Workspace Actions
Overview
The node provides integration with the TexAu Cloud platform, allowing users to perform various operations on different resources managed by TexAu. Specifically, for the Workspace - Update operation, it enables updating the details of an existing workspace by specifying its identifier and new name.
This operation is useful when you want to rename or modify a workspace's metadata without recreating it. For example, if your team reorganizes projects and wants to update workspace names to reflect new priorities or ownership, this node operation can automate that process within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Workspace ID | The unique identifier of the workspace to update. This is required and used in the URL path of the API request. |
| Workspace Name | The new name to assign to the workspace. This is a required string sent in the request body. |
Output
The node outputs the JSON response returned from the TexAu API after updating the workspace. This typically includes the updated workspace details such as its ID, name, and possibly other metadata fields reflecting the current state after the update.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the TexAu Cloud API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is
https://v2-prod-api.texau.com. - The node uses HTTP PUT method to send update requests to
/api/v1/public/workspaces/{{workspaceId}}.
Troubleshooting
- Invalid Workspace ID: If the provided workspace ID does not exist or is malformed, the API will likely return a 404 or validation error. Verify the workspace ID is correct.
- Missing Required Fields: Both Workspace ID and Workspace Name are required. Omitting either will cause the request to fail.
- Authentication Errors: Ensure the API key credential is valid and has permissions to update workspaces.
- API Rate Limits: Frequent updates may hit rate limits imposed by TexAu; handle errors accordingly.
- Network Issues: Connectivity problems can cause request failures; check network access to the TexAu API endpoint.
Links and References
- TexAu API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how routing and requests are structured in custom nodes