Lark Wiki

I. API Basic Information

https://open.feishu.cn/open-apis/wiki/v2

Authorization: Bearer {tenant_access_token}

application/json

II. Knowledge Spaces

1. Create Knowledge Space

POST /open-apis/wiki/v2/spaces

{ "name": "Wiki Name" }

1. Permission Penetration: The robot has no default permission to maintain the space after creation. It is strongly recommended to use the "Group Authorization Method"：
   • Create a group that includes the robot.
   • In the Wiki's [Settings] - [Member Settings], add this group as an "Administrator".
   • This way, the robot can obtain operation permissions for all pages in the space through the group identity.
2. Scenario Suggestion: Suitable for building a knowledge middle platform for new business lines.

2. Get Knowledge Space List

GET /open-apis/wiki/v2/spaces

III. Page Nodes

3. Create Wiki Page Node

POST /open-apis/wiki/v2/spaces/{space_id}/nodes

{
  "obj_type": "docx",
  "title": "Page Title",
  "parent_node_token": "wikcnXXX"
}

• Wiki nodes are essentially mounts of Docx files

• obj_type

  can be

  docx

  (document),

  sheet

  (spreadsheet),

  bitable

  (base) etc.
• After creation, you can use the

  feishu-doc-writer

  Skill to write content to the document
• If

  parent_node_token

  is empty, the node will be created in the root directory

4. Get Node Information

GET /open-apis/wiki/v2/spaces/{space_id}/nodes/{node_token}

5. Move Node

POST /open-apis/wiki/v2/spaces/{space_id}/nodes/{node_token}/move

IV. Best Practices

1. Structure First: Plan the directory structure of the Wiki first, then create nodes in batches
2. Document Mounting: Wiki nodes are essentially mount points for documents; use

   feishu-doc-writer

   for content writing
3. Permission Management: Configure access permissions promptly after creating a space
4. SOP Archiving: Precipitate stable operation processes into Wiki pages to form team knowledge assets

feishu-wiki Skill Summary (Desensitized Tutorial Version)

I. Core Function List

II. Typical Business Scenarios

• Scenario: After the project team completes a review discussion of a complex task, AI automatically extracts core steps, converts them into standard SOP documents, and accurately mounts them to the "Standardized Processes" category of the company Wiki.
• Value: Instantly solidifies fragmented experience into organizational assets, solving the problem of "experience loss when personnel leave".

• Scenario: When a new project is initiated, AI automatically creates a parent node named after the project in the team Wiki, and presets standardized secondary child nodes such as "PRD", "Requirement Pool", and "Meeting Minutes".
• Value: Realizes "standardization upon entry" for project documents, ensuring team members can collaborate within the preset framework from the first day of the project.

• Scenario: When the company restructures its Wiki, AI automatically scans existing isolated documents, identifies their business tags, and automatically moves/mounts them to the corresponding Wiki directory tree according to classification logic.
• Value: Greatly reduces the administrative cost of manually maintaining massive Wiki assets, enabling dynamic evolution of the knowledge system.

III. Practical Notes (Must Include in Tutorial · As Detailed As Possible)

• Risk: Due to Lark tenant security policies, robots often receive permission errors (403) when directly creating "top-level knowledge spaces" via API. In addition, even if the space is created, the robot may have no operation permissions for nodes in the space by default.
• Solution: The tutorial must emphasize the "Best Practice of Group Authorization":
  1. Manually create a [Group] that includes the robot.
  2. In the Wiki space settings, add this group as an [Administrator].
  3. This way, the robot can obtain permissions to create, move and edit all pages in the space through the group identity.

• Pitfall: This is the most easily confused technical point.

  node_token

  represents a "location node" on the Wiki directory; while

  obj_token

  is the actual document file behind it.
• Suggestion: Before performing the "content writing" operation, be sure to obtain the

  obj_token

  via the

  get_node

  interface, otherwise you cannot call the document writing interface.

• Note: When calling the Wiki node creation interface, the

  node_type

  field is usually required. In automated mounting scenarios, it is generally sufficient to set it to

  origin

  by default.

• Tip: When executing

  move_node

  (move node), the Lark API requires both

  target_parent_token

  (target directory) and

  target_space_id

  (target space) to be provided. Even when moving within the same space, it is recommended to explicitly complete these two parameters, otherwise 400 validation errors are easily triggered.

opensource/feishu-skills/feishu-wiki/SUMMARY.md