Lark Attendance icon

Lark Attendance

Lark Attendance Management

Overview

The node "Lark Attendance" is designed to interact with the Lark (Feishu) Attendance Management API, specifically to retrieve user attendance data. It allows users to query attendance records for specified employees within a given date range. 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 include:

  • Fetching attendance data for a list of employees over a specific period.
  • Automating daily or monthly attendance audits.
  • Integrating attendance information into other business intelligence tools.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
Employee Type Type of employee identifier used; options are employee_id or employee_no.
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 identifiers (strings) for whom attendance data will be fetched.
Custom Body JSON object allowing the user to specify a custom request body instead of using individual fields.
Options > 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 records retrieved from the Lark Attendance API. The structure typically includes attendance details per user for the requested date range. The exact schema depends on the API response but generally contains user IDs, timestamps, attendance status, and related metadata.

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

Dependencies

  • Requires an API key credential for authentication, either via a Tenant Token or OAuth2 token.
  • Connects to the Lark Suite open API endpoint at https://open.larksuite.com/open-apis.
  • Proper configuration of credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Common Issues:

    • Incorrect or expired authentication tokens leading to authorization errors.
    • Invalid date ranges (e.g., check_date_from greater than check_date_to) causing API rejections.
    • Empty or malformed user ID lists resulting in no data returned.
    • Using the custom body option incorrectly formatted JSON may cause request failures.
  • Error Messages:

    • Authorization errors: Ensure that the provided API credentials are valid and have sufficient permissions.
    • Validation errors: Verify that all required fields (dates, user IDs) are correctly set and formatted.
    • Network or timeout errors: Check network connectivity and API availability.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion