Lark Attendance

Lark Attendance Management

Actions22

Attendance Group Actions
Attendance Shift Actions
Attendance Schedule Actions
- Query Schedule Information
- Create Or Modify Schedule
Attendance Statistic Actions
Attendance Record Actions
Attendance Correction Actions
- Obtain Correction Record
User Setting Actions
- Modify User Settings
File Actions
- Upload Files
Task Actions
- Get User Attendance Data
- Add Approved Data In Feishu Attendance

Overview

The node "Lark Attendance" provides integration with Lark's attendance management system. Specifically, the Batch Query Attendance Flow Record operation allows users to query multiple employees' attendance flow records within a specified time range in a single batch request.

This node is beneficial for HR teams or administrators who need to retrieve attendance data for multiple employees efficiently, such as generating attendance reports, monitoring employee check-in/out times, or integrating attendance data into other systems.

Practical examples:

Fetching attendance records of all employees in a department for a given week.
Automating daily attendance data retrieval for payroll processing.
Monitoring attendance patterns by querying multiple user IDs at once.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
Employee Type	Specifies the type of employee ID used in the request and response (e.g., employee number, email).
Check Time From	Start datetime string to specify the beginning of the attendance record query period.
Check Time To	End datetime string to specify the end of the attendance record query period.
User Ids	A collection of user IDs (strings) representing employees whose attendance records are being queried.
Custom Body	JSON object allowing the user to provide a fully custom request body instead of using the standard fields.
Use Custom Body	Boolean flag indicating whether to send the custom JSON body instead of the standard structured inputs.

Output

The output contains a json field with the attendance flow records for the requested users within the specified time range. Each record typically includes user identifiers, timestamps, and attendance status details.

If binary data were involved (not indicated here), it would represent attachments or files related to attendance, but this node focuses on JSON data responses.

Dependencies

Requires an API key credential or OAuth2 token for authenticating requests to Lark's Open APIs.
The base URL for API requests is https://open.larksuite.com/open-apis.
Proper configuration of credentials in n8n is necessary before using this node.

Troubleshooting

Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Incorrect date formats for Check Time From or Check Time To may result in request failures.
- Providing empty or invalid user IDs can lead to empty or error responses.
- Using the custom body option incorrectly (malformed JSON) may cause the API to reject the request.
Error messages:
- Authorization errors: Ensure that the selected authentication method is correctly configured and tokens are valid.
- Validation errors: Verify that required fields like check_time_from, check_time_to, and user_ids are properly set.
- API rate limits: If too many requests are sent in a short time, wait and retry later.