lark-workflow-bitable-sync

Name: lark-workflow-bitable-sync
Availability: InStock
Author: liangdabiao

Automate data synchronization between two Lark Bitable tables with field mapping.

60|8|Updated Mar 31, 2026

Search Tags:#data synchronization #data mapping #incremental sync #cross-table #lark bitable

Ready to run

npx skills add https://github.com/liangdabiao/lark-workflow-feishu-cli --skill lark-workflow-bitable-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lark-workflow-bitable-sync
Source: https://github.com/liangdabiao/lark-workflow-feishu-cli/tree/main/.claude/skills/lark-workflow-bitable-sync
Command: npx skills add https://github.com/liangdabiao/lark-workflow-feishu-cli --skill lark-workflow-bitable-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of synchronizing data across tables in Lark Bitable, eliminating manual data entry and reducing errors.

Core Features & Use Cases

Cross-Table Data Synchronization: Automates the comparison and synchronization of data between two tables, ensuring consistency.
Field Mapping: Allows for custom mapping of fields between source and target tables.
Incremental Sync: Synchronizes only the changed records, optimizing performance.
Change Reporting: Provides a report of the changes made during synchronization.
Use Case: Ideal for scenarios where data needs to be consistently updated across multiple tables, such as merging customer information from different sources.

Quick Start

To initiate the synchronization process, use the command: "Start data synchronization between Table A and Table B."

Frequently Asked Questions about lark-workflow-bitable-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate data synchronization between two tables in Lark Bitable?▼

Incremental sync optimizes performance by identifying and transferring only the changed records between source and target tables, rather than scanning and rewriting the entire dataset during the synchronization process.

How does incremental sync work for cross-table data mapping?▼

Do I need Lark CLI to sync data across Lark Bitable tables?▼

Field mapping allows you to define custom correspondences between source and target fields. This ensures that data from different sources merges correctly into the appropriate columns during synchronization.

Can I customize field mapping when merging customer information in Lark Bitable?▼

Does Lark Bitable provide a change report after cross-table synchronization?▼

Yes, the synchronization process provides a change report detailing the modifications made. This helps track data consistency and updates across the synchronized tables.