Actions22
- Attendance Group Actions
- Attendance Shift Actions
- Attendance Schedule Actions
- Attendance Statistic Actions
- Attendance Record Actions
- Attendance Correction Actions
- User Setting Actions
- File Actions
- Task Actions
Overview
The "Lark Attendance" node integrates with Lark's Attendance Management API to manage attendance-related data. Specifically, the "Obtain Shift Details" operation under the "Attendance Shift" resource retrieves detailed information about a specific work shift by its unique ID. This is useful for HR teams or managers who want to fetch shift configurations, timings, or other metadata programmatically.
Practical examples include:
- Automatically fetching shift details to display in internal dashboards.
- Integrating shift data into payroll or scheduling systems.
- Validating shift configurations before assigning employees.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" (using a tenant-level API token) or "OAuth2" (using OAuth 2.0 authentication). |
| Shift Id | The unique numeric identifier of the shift whose details are to be obtained. This ID can be retrieved by searching shifts by name or creating a new shift via the Lark Attendance API. This property is required. |
| Options | Additional optional settings for the request. Currently supports: - Use Custom Body: A boolean flag indicating whether to send a custom request body instead of the default one. Defaults to false. |
Output
The node outputs JSON data containing the detailed information of the specified shift. This typically includes fields such as shift name, start and end times, break periods, and other configuration details defined in the Lark Attendance system.
If binary data were involved (not indicated here), it would represent files or attachments related to the shift, but this operation focuses on JSON data only.
Dependencies
- Requires access to Lark's Open APIs for Attendance Management.
- Needs either a valid Tenant Token or OAuth2 credentials configured in n8n to authenticate API requests.
- Network connectivity to
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid Shift Id: If the provided shift ID does not exist or is incorrect, the API will return an error. Verify the shift ID by searching or creating shifts beforehand.
- Authentication Errors: Ensure that the selected authentication method is correctly configured with valid credentials. Expired or invalid tokens will cause authorization failures.
- API Rate Limits: Frequent calls may hit rate limits imposed by Lark. Implement retries or backoff strategies if needed.
- Use Custom Body Misconfiguration: If "Use Custom Body" is enabled without providing a proper body, the request may fail. Only enable this option if you intend to customize the request payload.