Feishu Tencent Docs DingTalk Spreadsheet Automation

What problem it addresses

Teams often store spreadsheet data across Feishu, Tencent Docs, DingTalk, and Kingsoft Docs, but automation is blocked by platform differences: personal versus enterprise permissions, app review, app_secret, access_token, QPS limits, field types, and formula overwrite risks. Writing ad hoc API code can turn into repeated debugging across auth, approvals, bots, and scheduled jobs.

How the skill works

The skill starts by selecting the right integration path:
- Clarify the scenario: whether the target sheet is personal or enterprise, and whether it needs approvals, group bot push, scheduled aggregation, or cross-platform consolidation.
- Choose the mechanism: prefer a group webhook when possible; if spreadsheet read/write is required, compare Feishu sheets, bitable, Tencent Docs Open Platform, and DingTalk Smart Sheet APIs.
- Generate a skeleton: extract spreadsheet_token, sheetId, or document_id, configure tenant_access_token, OAuth flow, field types, retries, and backoff for batch calls.
- Cover common traps: access_token expires around two hours, date fields may require millisecond timestamps, attachments need an upload step to obtain file_token, and writes can overwrite formula cells.

Boundaries and notes

It is useful for choosing an automation path, drafting code skeletons, and diagnosing permission or rate-limit issues. It does not call the user's enterprise APIs on their behalf, store secrets, advise bypassing platform review, or treat RPA as the main solution. If a team must use Kingsoft Docs and open capabilities are weak, exporting xlsx for local processing may be more practical.