Actions38
- User Actions
- Department Actions
- User Group Actions
- User Group Member Actions
- Unit Actions
- Workforce Type Actions
- Custom User Field Actions
- Contact Scope Actions
Overview
This node manages user contacts within the Lark platform, specifically allowing deletion of a user by their User ID. It is useful in scenarios where you need to programmatically remove users from your organization's contact list or directory managed via Lark. For example, when an employee leaves the company, this node can automate the removal of their user record from Lark Contacts.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" (a token scoped to the tenant) or "OAuth2". |
| User Id | The unique identifier of the user to delete. Must match the expected user ID type in the API query. |
| Options | Additional optional settings: • Use Custom Body: Whether to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to delete the user. This typically includes success status and any relevant messages or error details returned by the API. There is no binary output.
Dependencies
- Requires valid authentication credentials: either a Tenant Token or OAuth2 token configured in n8n.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Proper permissions are needed on the provided credentials to delete users.
Troubleshooting
- Invalid User ID: If the User ID does not exist or is malformed, the API will return an error. Verify the User ID matches the expected format and exists in Lark.
- Authentication Errors: Using incorrect or expired tokens will cause authentication failures. Ensure the selected authentication method is correctly configured and tokens are valid.
- Permission Denied: The authenticated user must have rights to delete users. Check API permissions and roles.
- Use Custom Body Option: Enabling this without providing a proper body may cause request errors. Only enable if you intend to customize the request payload.