Lark Attendance icon

Lark Attendance

Lark Attendance Management

Actions22

Overview

The "Lark Attendance" node provides integration with Lark's attendance management system, specifically allowing users to query attendance statistics headers. This operation is useful for organizations that want to retrieve summarized attendance data over a specified period, filtered by employee type and other parameters.

Common scenarios include:

  • Generating attendance reports for HR or management.
  • Integrating attendance data into dashboards or analytics tools.
  • Automating attendance data retrieval for payroll or compliance purposes.

For example, an HR team could use this node to fetch attendance statistics between two dates for full-time employees, then process or visualize the data in their workflow.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
Employee Type Type of employee ID used in the response body (e.g., employee number, email).
End Date The end timestamp (number) for the attendance statistics query period.
Locale Locale string to specify language or regional settings for the response.
Start Date The start timestamp (number) for the attendance statistics query period.
Stats Type Type of statistics to query (e.g., daily, monthly, custom types defined by the API).
Custom Body JSON object to send as a custom request body instead of using individual parameters.
Use Custom Body Boolean option to toggle whether to send the custom JSON body or use the standard parameters.

Output

The node outputs JSON data containing the queried attendance statistics headers. The structure typically includes metadata about the statistics such as date ranges, employee identifiers, and aggregated attendance metrics. The exact fields depend on the API response from Lark's attendance service.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication credentials via either a tenant token or OAuth2 token.
  • Depends on access to Lark's open APIs at https://open.larksuite.com/open-apis.
  • Proper configuration of credentials within n8n is necessary to authenticate requests.

Troubleshooting

  • Authentication errors: Ensure that the correct authentication method is selected and that the provided token or OAuth2 credentials are valid and have sufficient permissions.
  • Invalid date range: The start and end dates should be valid timestamps; otherwise, the API may return errors or empty results.
  • Incorrect employee type: Using an unsupported or incorrect employee type may cause the API to reject the request or return incomplete data.
  • Custom body issues: When using the custom body option, ensure the JSON is well-formed and matches the expected schema of the API.
  • API rate limits or network issues: Temporary failures might occur due to rate limiting or connectivity problems; retrying after some time can help.

Links and References

Discussion