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 contacts within the Lark platform, specifically focusing on organizational units and departments. The "Dissociate A Department With A Unit" operation removes the association between a specified department and a unit. This is useful in scenarios where organizational restructuring occurs, such as when a department is moved out of a unit or when cleaning up outdated associations.
Practical examples include:
- Removing a department from a unit after a reorganization.
- Correcting erroneous links between departments and units.
- Automating cleanup of department-unit relationships during data synchronization.
Properties
Name | Meaning |
---|---|
Authentication | Method to authenticate API requests; options are "Tenant Token" or "OAuth2". |
Department Id | The unique identifier of the department to dissociate from the unit. |
Department Id Type | The type or format of the department ID provided (e.g., internal ID, external ID). |
Unit Id | The unique identifier of the unit from which the department will be dissociated. |
Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of the standard fields. |
Custom Body | A JSON object allowing full customization of the request body for advanced use cases. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to dissociate the department from the unit. This typically includes status information about the success or failure of the operation. There is no binary data output.
Dependencies
- Requires an active connection to the Lark Open API.
- Needs either a Tenant Token or OAuth2 authentication configured in n8n credentials.
- The base URL for API requests is
https://open.larksuite.com/open-apis
. - Proper permissions must be granted to the API token to manage contacts and organizational units.
Troubleshooting
- Invalid or missing IDs: Ensure that the Department Id, Department Id Type, and Unit Id are correctly specified and correspond to existing entities in Lark.
- Authentication errors: Verify that the selected authentication method is properly configured and the token has not expired.
- API permission issues: Confirm that the API credentials have sufficient rights to modify organizational structures.
- Custom Body usage: When using a custom body, ensure the JSON structure matches the API requirements exactly to avoid malformed request errors.
- Network or connectivity problems: Check internet access and Lark API service status if requests fail unexpectedly.