Log daily department attendance to Lark Base with Lark
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every day at 23:00). It uses only n8n's built-in nodes. It also calls open.larksuite.com over HTTP.
How it runs
Trigger: On a schedule (every day at 23:00).
- Template Config (Edit Fields (Set)): sets 11 fields: app_id, app_secret, department_id…
- Get Tenant Access Token (HTTP Request): calls open.larksuite.com (POST)
- Get Department Users (HTTP Request): calls open.larksuite.com
- Normalize User Fields (Code): runs custom JavaScript code
- Get Daily Attendance Records (HTTP Request): calls open.larksuite.com (POST)
- Build Bitable Batch Records (Code): runs custom JavaScript code
- Create Bitable Records (HTTP Request): calls an HTTP API (POST)
HTTP calls to: open.larksuite.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code
From the author
Quick overview This workflow runs daily (or manually) to pull attendance logs for all users in a Lark department via the Lark Open Platform APIs, then writes each user’s first check-in and last check-out into a Lark Base (Bitable) table in batches. How it…