Lark Attendance icon

Lark Attendance

Lark Attendance Management

Actions22

Overview

The node integrates with Lark Attendance Management to create or modify attendance schedules for users. It allows specifying daily shifts for employees, enabling automated management of work schedules within the Lark ecosystem. This is useful for HR teams or administrators who want to programmatically update or set employee shift schedules without manual entry in the Lark platform.

Practical examples:

  • Automatically assigning monthly shifts to employees based on a predefined roster.
  • Modifying existing schedules when there are changes in shift patterns or employee assignments.
  • Bulk updating user shifts for specific days and months via API calls.

Properties

Name Meaning
Authentication Method of authenticating API requests: either using a Tenant Token or OAuth2 authentication.
Employee Type Specifies the type of employee ID used for user_id in both request and response bodies.
User Daily Shifts A collection of daily shift entries, each containing:
- day_no: Day number
- group_id: Group identifier
- month: Month number
- shift_id: Shift identifier
- user_id: User identifier
Custom Body Allows sending a fully custom JSON body instead of using the structured properties. Useful for advanced use cases or when the default structure does not fit requirements.
Options > Use Custom Body Boolean flag to toggle between using the structured input fields (User Daily Shifts) or the Custom Body JSON.

Output

The node outputs JSON data representing the response from the Lark Attendance API after creating or modifying schedules. The output typically includes confirmation of the scheduled shifts per user, reflecting the submitted data and any additional metadata returned by the API.

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

Dependencies

  • Requires an API key credential for authentication, either a Tenant Token or OAuth2 token configured in n8n.
  • Connects to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • No other external dependencies are indicated.

Troubleshooting

  • Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided. Expired or invalid tokens will cause failures.
  • Invalid input format: When not using the custom body, ensure all required fields in User Daily Shifts are correctly filled and formatted.
  • API errors: The Lark API may return errors if shift IDs, user IDs, or group IDs do not exist or are invalid. Verify these values against your Lark tenant data.
  • Using Custom Body: If enabled, the JSON must be well-formed and match the expected API schema; otherwise, the request will fail.

Links and References

Discussion