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

The node "Lark Attendance" provides integration with Lark's attendance management system. Specifically, the "Delete Shift" operation under the "Attendance Shift" resource allows users to delete a specific work shift from their attendance records by specifying its unique Shift ID.

This node is useful in scenarios where an organization needs to manage and maintain accurate attendance shifts, such as removing outdated or incorrect shift definitions. For example, if a shift schedule changes or a shift was created by mistake, this operation can be used to clean up the attendance data accordingly.

Properties

Name	Meaning
Authentication	Method of authentication to use for API requests. Options: Tenant Token, OAuth2.
Shift Id	The unique identifier of the shift to delete. This ID can be obtained by searching shifts by name or creating a new shift. Required field.
Options	Additional optional settings: • Use Custom Body: Whether to send a custom request body instead of the default one (boolean).

Output

The node outputs JSON data representing the response from the Lark Attendance API after attempting to delete the specified shift. Typically, this will include confirmation of deletion or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

Requires access to Lark's Open API for attendance management.
Requires either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
Network connectivity to https://open.larksuite.com/open-apis.

Troubleshooting

Common issues:
- Invalid or missing Shift ID: Ensure the Shift ID provided exists and is correct.
- Authentication errors: Verify that the selected authentication method is properly configured and valid.
- Permission denied: The authenticated user must have rights to delete shifts.
- API rate limits or network issues may cause failures.
Error messages:
- "Shift not found": The Shift ID does not correspond to any existing shift.
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Bad Request": Possibly due to malformed input or using custom body incorrectly.

Resolving these typically involves verifying input parameters, checking credentials, and ensuring proper API usage.