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

This node, named "Lark Attendance," is designed to interact with Lark's attendance management system via its API. It facilitates operations related to managing attendance data within the Lark Suite environment. Typical use cases include automating attendance record retrieval, updating attendance information, or integrating attendance data into workflows for HR or team management purposes.

For example, a user might employ this node to automatically fetch daily attendance reports from Lark and process them further in an n8n workflow, such as sending notifications or generating summaries.

Properties

Name	Meaning
Authentication	Method of authenticating API requests. Options: - Tenant Token - OAuth2
Options	Additional optional settings: - Use Custom Body (boolean): Whether to send a custom request body instead of the default one

Output

The node outputs JSON data representing the response from the Lark Attendance API. This typically includes attendance records, status messages, or confirmation of actions performed. The exact structure depends on the specific API endpoint called and the operation executed.

If binary data were involved (e.g., file downloads), it would be indicated here, but based on the provided code and properties, the output is JSON only.

Dependencies

Requires valid authentication credentials for Lark Suite API access, either via a Tenant Token or OAuth2.
The node communicates with the Lark Suite open APIs at https://open.larksuite.com/open-apis.
Proper configuration of these credentials in n8n is necessary before using the node.

Troubleshooting

Authentication errors: Ensure that the selected authentication method is correctly configured with valid tokens or OAuth credentials.
API request failures: Check network connectivity and verify that the Lark Suite API service is operational.
Invalid custom body usage: If "Use Custom Body" is enabled, ensure the custom body format matches the API requirements to avoid request errors.
Missing or incorrect parameters: Verify all required input properties are set correctly according to the API documentation.