Build agents
Sync Feishu and DingTalk tables
Sync Feishu Bitable or DingTalk AI Table one way into a workbook for agents to analyze.
Table connectors sync Feishu Bitable or DingTalk AI Table one way into an AskTable workbook. Synced sheets can be queried by agents like any other data, while the content continues to be maintained in Feishu or DingTalk.
This requires a project owner or project administrator. Entry: “More” → “Data intake” → “Connectors”.
Prepare
- Feishu: create an “internal enterprise app” on the Feishu Open Platform, note the App ID and App Secret, and grant the app read access to the target Bitable.
- DingTalk: prepare an internal enterprise app with read access to the source table, and an operator ID.
- The table's share link.
“How do I create an app and grant permissions?” and “How do I grant the app access to the table?” on the page give detailed guidance. App secrets are stored encrypted on the server only.
Create a sync
Choose a source
Click “Connect Feishu Bitable” or “Connect DingTalk AI Table”.
Configure app authorization
Enter an app authorization name and the app credentials. Saved apps can be reused without entering the secret again.
Read the table and choose sub-tables
Paste the table share link, click “Read table”, and select the sub-tables to sync; you can select several.
Choose the target workbook and frequency
Choose an existing workbook or create one. Sync frequency can be “Manual only”, “Hourly”, or “Daily at 08:00 (Beijing time)”. Click “Save and sync”.
Day-to-day management
- Click “Sync now” to sync manually; “Pause schedule” and “Resume schedule” control scheduled syncs.
- The list shows each sync task's status, last sync time, and row count.
- Synced sheets are marked “Synced from source · Read-only” in the workbook and cannot be edited in AskTable. To change data, edit it in Feishu or DingTalk and sync again. Sheets created manually in the same workbook are not affected.
- Remove app authorizations that are no longer used with “Remove unused authorizations”.
Workbooks created with the earlier “Sync from Feishu Bitable” keep their configuration, sub-table bindings, and data after upgrade and are managed in connectors. Integrators that call the old Feishu sync API directly must switch to the unified connector API.
Common issues
| Message | Cause | Action |
|---|---|---|
| The app or operator has no read permission | The app has not been granted read access to the table | Grant access in Feishu or DingTalk |
| The app credentials are invalid | The App Secret or other credentials are wrong or have changed | Update the credentials in “Settings” |
| The source was deleted or is inaccessible | The original table was deleted or the share link no longer works | Choose the source again |
| The source response was incomplete | The source service returned an error; existing data is kept | Try again later |
| Sync timed out | Large data volume or slow network | Sync again |
| Sync failed | Problems with source permissions or field data | Check source permissions and field content, then retry |