Actions22
- Attendance Group Actions
- Attendance Shift Actions
- Attendance Schedule Actions
- Attendance Statistic Actions
- Attendance Record Actions
- Attendance Correction Actions
- User Setting Actions
- File Actions
- Task Actions
Overview
The "Lark Attendance" node integrates with Lark's Attendance Management API to obtain detailed information about a specific attendance group. This operation is useful for HR and administrative workflows where you need to retrieve attendance group configurations or details for reporting, auditing, or further processing.
Typical use cases include:
- Fetching attendance group details to verify group membership or settings.
- Integrating attendance data into payroll or employee management systems.
- Automating attendance-related notifications or compliance checks.
For example, after creating or modifying an attendance group in Lark, you can use this node to programmatically retrieve the group's details by specifying its ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access the Lark API. Options: Tenant Token, OAuth2. |
| Employee Type | Specifies the type of user ID used in requests (e.g., employee ID, email). This affects how user identifiers are interpreted when querying attendance data. |
| Dept Type | Specifies the type of department ID used in requests. Determines how department identifiers are interpreted. |
| Group Id | Required. The unique identifier of the attendance group whose details you want to obtain. This ID can be retrieved by creating/modifying attendance groups, searching groups by name, or querying attendance results. |
| Options | Additional options for the request. Currently supports: • Use Custom Body: Whether to send a custom request body instead of the default one. |
Output
The node outputs JSON data containing the detailed information of the specified attendance group. This typically includes group metadata such as group name, members, schedules, and other configuration details relevant to attendance tracking.
If the node supports binary data output (not indicated here), it would represent attachments or files related to attendance records, but this is not applicable based on the provided code.
Dependencies
- Requires valid authentication credentials for Lark's API, either via a Tenant Token or OAuth2.
- Needs network access to
https://open.larksuite.com/open-apis. - Proper configuration of authentication credentials within n8n is necessary before using this node.
Troubleshooting
- Missing or invalid Group Id: The node requires a valid attendance group ID. Ensure the ID is correct and corresponds to an existing group.
- Authentication errors: Verify that the selected authentication method is correctly configured and the token or OAuth credentials are valid and have sufficient permissions.
- API rate limits or connectivity issues: Network problems or exceeding API quotas may cause failures. Check your network connection and API usage limits.
- Incorrect Employee Type or Dept Type: Using unsupported or incorrect types might result in unexpected responses or errors. Confirm these values match those expected by the Lark API.