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 "Lark Attendance" node integrates with Lark's Attendance Management API to obtain attendance records for employees. Specifically, the "Obtain Attendance Results" operation fetches attendance data within a specified date range for selected users. This node is useful in HR automation workflows where attendance tracking and reporting are required, such as generating attendance reports, monitoring employee presence, or integrating attendance data into payroll systems.

Practical examples:

Automatically retrieve attendance results for a group of employees over a pay period.
Trigger alerts if attendance data shows anomalies or absences.
Aggregate attendance data for performance reviews or compliance audits.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
Employee Type	Specifies the type of employee ID used (e.g., internal ID, email).
Check Date From	Start timestamp (number) for the attendance data query range.
Check Date To	End timestamp (number) for the attendance data query range.
User Ids	List of user IDs (strings) for whom to obtain attendance results.
Custom Body	JSON object allowing a fully custom request body to be sent instead of using individual fields.
Use Custom Body	Boolean flag indicating whether to send the custom JSON body instead of the standard parameters.

Output

The node outputs JSON data containing the attendance results retrieved from the Lark Attendance API. The structure typically includes attendance records per user within the requested date range, detailing check-in/check-out times and statuses.

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

Dependencies

Requires an active connection to Lark's Open APIs.
Needs either a Tenant Token credential or OAuth2 authentication configured in n8n.
Network access to https://open.larksuite.com/open-apis must be available.

Troubleshooting

Authentication errors: Ensure that the correct authentication method is selected and credentials are valid and not expired.
Invalid date range: The check_date_from and check_date_to should be valid timestamps; otherwise, the API may reject the request.
Empty user IDs: Providing no user IDs will likely result in no data returned or an error; ensure at least one user ID is specified.
Custom Body usage: When using the custom body option, ensure the JSON is correctly formatted and contains all required fields expected by the API.
API rate limits: Frequent requests might hit rate limits imposed by Lark; handle such errors by implementing retries or backoff strategies.