Actions22
- Kanban Actions
- Meeting Actions
- Project Actions
- Team Actions
- User Actions
Overview
The node named "Workspace" provides integration with a Workspace API, allowing users to get and modify data related to various resources such as Kanban boards, Meetings, Projects, Teams, and Users. Specifically, for the User resource and the Update User Password operation, this node enables updating the password of an existing user by specifying their unique user ID and the new password.
This functionality is beneficial in scenarios where automated workflows need to manage user credentials securely, such as resetting passwords after a security event or synchronizing user accounts across systems.
Example use case:
An administrator can create an automation that triggers when a user requests a password reset, then uses this node to update the user's password in the Workspace system automatically.
Properties
| Name | Meaning |
|---|---|
| User ID | Unique identifier of the user whose password will be updated. |
| Password | New password to set for the specified user. |
Output
The node outputs JSON data representing the result of the password update operation. This typically includes confirmation of success or details about the updated user record. The exact structure depends on the Workspace API's response but generally confirms that the password was changed.
No binary data output is indicated.
Dependencies
- Requires connection to the Workspace API.
- Needs an API key credential and tenant information configured in the node's credentials.
- The base URL for the API must be provided via credentials.
- HTTP headers include
Accept: application/json,Content-Type: application/json, and authentication headers (APIKEYandTENANT).
Troubleshooting
Common issues:
- Invalid or missing User ID: Ensure the User ID corresponds to an existing user.
- Insufficient permissions: The API key used must have rights to update user passwords.
- Incorrect API credentials or base URL: Verify that the API key, tenant, and URL are correctly configured.
- Password policy violations: The new password might not meet the Workspace system’s complexity requirements.
Error messages:
- Authentication errors (e.g., 401 Unauthorized): Check API key and tenant values.
- Validation errors (e.g., 400 Bad Request): Confirm that User ID and password fields are correctly filled and valid.
- Not found errors (e.g., 404 Not Found): The specified User ID does not exist.
Resolving these usually involves verifying input parameters and credentials, and consulting Workspace API documentation for password requirements.
Links and References
- Refer to the Workspace API documentation for detailed information on user management endpoints and password update requirements.
- n8n documentation on setting up API credentials and using HTTP request nodes may also be helpful.