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
The node "Lark Contacts" provides management capabilities for contacts within the Lark platform. Specifically, the "Delete Units" operation under the "Unit" resource allows users to delete a contact unit by specifying its unique identifier. This is useful in scenarios where organizational units or groups of contacts need to be removed from the system, such as cleaning up outdated departments or restructuring teams.
Practical examples include:
- Removing a department unit that no longer exists.
- Deleting a temporary project team unit after project completion.
- Automating cleanup of units based on external triggers or workflows.
Properties
Name | Meaning |
---|---|
Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
Unit Id | The unique identifier of the unit to be deleted. This is required. |
Options | Additional options for the request: currently supports "Use Custom Body" (boolean) to specify if a custom request body should be used. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to delete the specified unit. Typically, this will include status information indicating success or failure of the deletion operation.
If the node supports binary data output, it would represent any binary content returned by the API, but in this case, the operation deals with JSON responses only.
Dependencies
- Requires an active connection to the Lark Open API.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- The base URL for API requests is
https://open.larksuite.com/open-apis
. - Proper permissions must be granted to the API credentials to perform unit deletions.
Troubleshooting
Common issues:
- Invalid or missing Unit Id: The node requires a valid unit identifier; ensure the ID is correct and exists.
- Authentication errors: Verify that the provided API credentials are valid and have sufficient permissions.
- Network or API endpoint errors: Check connectivity and that the Lark API service is operational.
Error messages:
- Unauthorized or Forbidden: Indicates invalid credentials or insufficient permissions. Resolve by updating credentials or permissions.
- Not Found: The specified Unit Id does not exist. Confirm the ID before retrying.
- Bad Request: Possibly due to malformed input or incorrect parameters. Review the input properties.