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 provides integration with Lark's attendance management system, specifically allowing users to query schedule information for employees. This node is useful in scenarios where organizations want to automate the retrieval of employee attendance schedules within a specified date range. For example, HR teams can use this node to fetch work schedules for multiple employees over a period to analyze attendance patterns or prepare reports.

Properties

Name	Meaning
Authentication	Method of authentication to access the API: either using a Tenant Token or OAuth2 credentials.
Employee Type	Specifies the type of employee ID used in requests and responses (e.g., internal ID, email, etc.).
Check Date From	Start timestamp (number) defining the beginning of the date range for querying schedules.
Check Date To	End timestamp (number) defining the end of the date range for querying schedules.
User Ids	A collection of user IDs (strings) for which to query schedule information. Multiple user IDs can be added.
Custom Body	JSON object allowing users to provide a fully custom request body instead of using the standard parameters.
Options > Use Custom Body	Boolean flag indicating whether to send the custom JSON body instead of the standard structured parameters.

Output

The node outputs JSON data containing the queried schedule information for the specified users within the given date range. The output includes user IDs and their corresponding schedule details as returned by the Lark Attendance API. No binary data output is involved.

Dependencies

Requires an active connection to Lark's Open API endpoint (https://open.larksuite.com/open-apis).
Requires authentication via either:
- A Tenant Token credential.
- An OAuth2 credential.
Proper configuration of these credentials in n8n is necessary to authenticate API requests.

Troubleshooting

Common Issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Incorrect date ranges (e.g., check_date_from greater than check_date_to) may result in empty or error responses.
- Providing invalid or unsupported employee types could lead to unexpected results or errors.
- If using the custom body option, malformed JSON or missing required fields may cause request failures.
Error Messages:
- Authorization errors typically indicate issues with the provided API credentials; verify and refresh tokens as needed.
- Validation errors from the API may indicate incorrect parameter formats or missing required fields.
- Network or connectivity errors suggest checking internet access or API endpoint availability.