Lark Attendance icon

Lark Attendance

Lark Attendance Management

Actions22

Overview

The "Add Approved Data In Feishu Attendance" operation in the Lark Attendance node allows users to submit approved attendance-related data into the Feishu (Lark) attendance system. This includes various types of attendance approvals such as leaves, outs (time out), overtime work, and business trips.

This node is useful for automating the integration of external or custom approval systems with Feishu's attendance management, ensuring that approved attendance records are synchronized without manual entry. For example, HR systems can push approved leave requests or overtime hours directly into Feishu attendance, streamlining payroll and attendance tracking.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2.
Employee Type The type of employee identifier used, either employee_id or employee_no. Determines how the employee is referenced in the request query string.
User Approval JSON object containing the approved attendance data to add. It includes arrays for different approval categories: leaves, outs, overtime_works, and trips. Each item can contain localized names and timing details.
Custom Body A fully customizable JSON body to send instead of the standard structured input. Allows advanced users to define the entire payload manually.
Options > Use Custom Body Boolean flag indicating whether to use the Custom Body property instead of the standard User Approval structure.

Output

The node outputs the response from the Feishu attendance API after submitting the approved data. The output is a JSON object reflecting the API's response, which typically includes confirmation of the added attendance records or error information if the submission failed.

No binary data output is involved.

Dependencies

  • Requires an active Feishu (Lark) API authentication credential, either via Tenant Token or OAuth2.
  • The node sends requests to the Feishu open API endpoint at https://open.larksuite.com/open-apis.
  • Proper permissions on the Feishu side to add attendance approval data are necessary.

Troubleshooting

  • Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials and has sufficient permissions.
  • Invalid employee identifiers: The employee_type must match the identifier used in the approval data; mismatches may cause API rejections.
  • Malformed JSON in User Approval or Custom Body: The JSON must be well-formed and follow the expected schema; otherwise, the API will return validation errors.
  • API rate limits or network issues: Temporary failures might occur due to rate limiting or connectivity problems; retrying after some time may help.
  • Using Custom Body: When enabled, ensure the custom JSON matches the API specification exactly, as no internal validation is performed by the node.

Links and References

Discussion