Lark Attendance icon

Lark Attendance

Lark Attendance Management

Actions22

Overview

The "Lark Attendance" node integrates with Lark's attendance management system, enabling automation of attendance-related tasks. Specifically, the Upload Files operation under the File resource allows users to upload files related to attendance records or reports to Lark's platform.

This node is beneficial in scenarios where organizations want to automate the submission or archival of attendance documents, such as uploading daily attendance logs, shift schedules, or compliance reports directly from workflows without manual intervention.

Practical examples include:

  • Automatically uploading attendance CSV files generated by another system at the end of each day.
  • Sending scanned attendance sheets or approval documents to Lark for centralized storage and processing.
  • Integrating with HR systems to push attendance evidence files into Lark’s attendance module.

Properties

Name Meaning
Authentication Method used to authenticate API requests. Options: Tenant Token, OAuth2
File Name The name of the file to be uploaded, including its suffix (e.g., .csv, .pdf).
Use Custom Body Boolean flag indicating whether to send a custom JSON body instead of the default request.
Custom Body A JSON object representing a custom request body to send when Use Custom Body is enabled.

Output

The node outputs JSON data representing the response from the Lark API after attempting to upload the file. This typically includes metadata about the uploaded file, status information, and any identifiers assigned by Lark.

If the node supports binary data input (not explicitly shown here), it would handle the file content accordingly, but the provided code and properties focus on JSON-based file upload parameters.

Dependencies

  • Requires an API authentication credential, either via a Tenant Token or OAuth2 method.
  • Connects to Lark's open API endpoint at https://open.larksuite.com/open-apis.
  • No additional external dependencies are indicated beyond standard HTTP requests to Lark's API.

Troubleshooting

  • Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials. Expired tokens or incorrect scopes can cause failures.
  • File name issues: The file name must include a proper suffix; missing or invalid file extensions might lead to rejection by the API.
  • Custom body usage: If using the custom body option, ensure the JSON structure matches the expected API schema; malformed JSON or incorrect fields will cause errors.
  • Network or API errors: Check connectivity and API availability. Rate limits or permission restrictions on the Lark side may also affect uploads.

Links and References

Discussion