Actions126
- User Actions
- Group Actions
- Content Actions
- Post Actions
- Comment Actions
- Like Actions
- Activity Actions
- Notification Actions
- Space Actions
- Calendar Actions
- CFile Directory Actions
- CFile Actions
- CFile Item Management Actions
- Survey Actions
- Task Actions
- Task List Actions
- Wiki Page Actions
- Mail Conversation Actions
- Mail Entry Actions
- Mail Recipient Actions
- Session Actions
- File Actions
- Space Membership Actions
- Topic Actions
- Survey Answer Actions
- Survey Answers Actions
- Wiki Page Revision Actions
- Mail Tag Actions
Overview
This node interacts with the HumHub API to perform various operations on the User resource, specifically supporting a 'Soft Delete' operation. The 'Soft Delete' operation marks a user as deleted without permanently removing their data, allowing for potential recovery or auditing. This is useful in scenarios where user data should be retained for compliance or restoration purposes rather than being fully erased.
Use Case Examples
- Soft delete a user by providing their user ID to mark them as deleted without permanent removal.
- Use the node to manage user lifecycle by soft deleting users who are no longer active but whose data must be preserved.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for the API request, either Basic Auth or JWT Token. |
| ID | The unique identifier of the user to be soft deleted. |
Output
JSON
id- The ID of the user that was soft deleted.status- The status or result of the soft delete operation returned by the API.
Dependencies
- HumHub API
Troubleshooting
- Ensure the user ID provided is valid and exists in the HumHub system to avoid errors.
- Authentication errors may occur if the provided credentials (Basic Auth or JWT Token) are incorrect or expired.
- API request failures could be due to network issues or incorrect API endpoint usage.
Links
- HumHub API Documentation - Official documentation for the HumHub API endpoints and usage.