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
This node integrates with Lark's Attendance Management system to obtain detailed attendance flow records for employees. It is particularly useful in HR automation workflows where you need to retrieve specific attendance data such as check-in/out times, approvals, or corrections related to an employee's attendance flow.
Typical use cases include:
- Fetching attendance flow records for auditing or payroll processing.
- Integrating attendance data into internal dashboards or reporting tools.
- Automating follow-up actions based on attendance anomalies or approvals.
For example, after batch querying attendance flows or importing new attendance records, this node can be used to fetch the detailed flow record by its unique ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token (using a tenant-level API token) or OAuth2 (using OAuth2 authentication). |
| Employee Type | Specifies the type of employee ID used for user_id and creator_id fields in the response body. This affects how user identifiers are interpreted. |
| User Flow Id | Required. The unique identifier of the attendance flow record to retrieve. This ID can be obtained from batch queries, attendance results queries, or import operations as referenced in the documentation. |
| Options | Additional optional settings. Currently supports: • Use Custom Body: Whether to send a custom request body instead of the default one. Defaults to false. |
Output
The node outputs JSON data representing the detailed attendance flow record corresponding to the provided User Flow Id. This includes information such as:
- Attendance flow metadata (timestamps, status).
- User-related IDs and types.
- Approval or correction details if applicable.
No binary data output is produced by this node.
Dependencies
- Requires access to Lark's Open API endpoints for attendance management.
- Needs either a tenant-level API token or OAuth2 credentials configured in n8n for authentication.
- Network connectivity to
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid or missing User Flow Id: Ensure that the
User Flow Idis correctly obtained from prior API calls or imports. An incorrect or missing ID will cause the API call to fail. - Authentication errors: Verify that the selected authentication method is properly configured with valid credentials. Expired tokens or misconfigured OAuth2 credentials will result in authorization failures.
- API rate limits or network issues: If requests fail intermittently, check for API rate limiting or network connectivity problems.
- Custom Body usage: If enabling "Use Custom Body," ensure the custom payload matches the API specification; otherwise, the request may be rejected.