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 functionality to manage and retrieve contact-related information from the Lark platform. Specifically, for the Resource "Department" and Operation "Obtain Parent Department Information," it fetches details about the parent department of a given department ID. This is useful in organizational management scenarios where hierarchical relationships between departments need to be understood or displayed.
Practical examples include:
- Displaying the parent department name or ID when viewing a department's details.
- Building organizational charts by traversing department hierarchies.
- Automating workflows that depend on department structure, such as approval routing or notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| Department Id | The unique identifier of the department whose parent information is to be obtained |
| Options | Additional optional settings: |
| - Use Custom Body | Whether to send a custom request body instead of default parameters (true/false) |
Output
The node outputs JSON data containing the parent department information corresponding to the provided department ID. The exact structure depends on the Lark API response but typically includes fields such as parent department ID, name, and other metadata describing the parent department.
If binary data were involved (not indicated here), it would represent files or attachments related to the department, but this operation focuses solely on JSON data.
Dependencies
- Requires an active connection to the Lark Open API endpoint (
https://open.larksuite.com/open-apis). - Needs either a Tenant Token or OAuth2 authentication credential configured in n8n.
- The node uses standard HTTP headers for JSON content type and accepts JSON responses.
Troubleshooting
- Invalid Department ID: If the department ID does not exist or is malformed, the API may return an error or empty result. Verify the department ID input.
- Authentication Errors: Ensure that the selected authentication method is correctly configured with valid credentials.
- API Rate Limits: Excessive requests might lead to rate limiting; handle retries or backoff accordingly.
- Use Custom Body Option: If enabled incorrectly, the request body might not match API expectations causing errors. Use only if you understand the required payload format.