Lark Attendance icon

Lark Attendance

Lark Attendance Management

Actions22

Overview

The node integrates with Lark Attendance Management to import attendance flow records. It allows users to submit detailed attendance data such as check-in times, locations, device information, and photos for employees. This is useful for organizations that want to automate the process of recording employee attendance from various sources or devices into the Lark platform.

Typical use cases include:

  • Importing bulk attendance data collected from external systems or devices.
  • Synchronizing attendance records from third-party applications into Lark.
  • Automating attendance tracking workflows by feeding custom attendance data programmatically.

Properties

Name Meaning
Authentication Method of authentication to access the Lark API. Options: Tenant Token, OAuth2.
Employee Type Specifies the type of employee ID used in user_id and creator_id fields within request and response.
Flow Records Collection of attendance flow record items to import. Each item includes fields like check time, location, device info, photos, etc.
Custom Body JSON object allowing users to provide a fully custom request body instead of using the predefined flow records structure.
Use Custom Body Boolean flag to toggle between using the predefined flow records input or sending a custom JSON body.

Details on Flow Records Item Fields (example item):

  • bssid: BSSID of WiFi network (string URL).
  • check_time: Timestamp of attendance check (string).
  • comment: Additional comments (string).
  • creator_id: ID of the creator of the record (string).
  • device_id: Device identifier (string).
  • is_field: Boolean indicating if the check was done in the field.
  • is_wifi: Boolean indicating if WiFi was used.
  • latitude, longitude: Geolocation coordinates (numbers).
  • location_name: Name of the location (string).
  • photo_urls: Array of URLs pointing to photos related to the attendance record.
  • record_id: Unique record identifier (string).
  • ssid: SSID of WiFi network (string URL).
  • type: Numeric type indicator (number).
  • user_id: Employee user ID (string).

Output

The node outputs the response from the Lark API after importing the attendance flow records. The output is structured as JSON containing details about the imported records, including any metadata or status information returned by the API.

If binary data is involved (e.g., photo URLs), it is referenced by URL strings rather than embedded directly.

Dependencies

  • Requires an active connection to the Lark Open API.
  • Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
  • Network access to https://open.larksuite.com/open-apis.

Troubleshooting

  • Authentication errors: Ensure the correct authentication method is selected and valid credentials are provided.
  • Invalid data format: Verify that the flow records conform to the expected schema, especially date/time formats and required fields.
  • API rate limits or quota exceeded: Check Lark API usage limits and adjust request frequency accordingly.
  • Network issues: Confirm connectivity to the Lark API endpoint.
  • Custom Body errors: When using a custom JSON body, ensure it matches the API specification exactly to avoid validation errors.

Links and References

Discussion