langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #9410] feat: datasource add feishu wiki import #26405

New Issue
Closed
opened 2026-02-21 20:39:31 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:39:31 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/9410

State: closed
Merged: No

Checklist:

  • Please open an issue before creating a PR or link to an existing issue
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

add lark wiki import by knowledge base

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update, included: Dify Document
  • Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
  • Dependency upgrade

Testing Instructions

  1. Create enterprise-built applications through Lark Open Platform (https://open.larkoffice.com/)
    image

  2. Configure the app_id and app_secret of the Lark application in dify.

# Feishu wiki import configuration, support public and internal
FEISHU_WIKI_INTEGRATION_TYPE=public
FEISHU_APP_ID=you-app-id
FEISHU_APP_SECRET=you-app-secret

  1. Bind the Feishu data source in "dify-settings-data source"
    image
    image
    image

  2. When creating a knowledge base, select Feishu Knowledge Base as the data source (Note: Currently Feishu Knowledge Base only supports docx type documents)
    image
    image
    image
    image

**Original Pull Request:** https://github.com/langgenius/dify/pull/9410 **State:** closed **Merged:** No --- # Checklist: - [x] Please open an issue before creating a PR or link to an existing issue - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods # Description add lark wiki import by knowledge base ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [ ] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement - [ ] Dependency upgrade # Testing Instructions 1. Create enterprise-built applications through Lark Open Platform (https://open.larkoffice.com/) ![image](https://github.com/user-attachments/assets/db0ca53c-15d8-472d-859b-f8aa98272963) 2. Configure the app_id and app_secret of the Lark application in dify. ``` # Feishu wiki import configuration, support public and internal FEISHU_WIKI_INTEGRATION_TYPE=public FEISHU_APP_ID=you-app-id FEISHU_APP_SECRET=you-app-secret ``` 3. Bind the Feishu data source in "dify-settings-data source" ![image](https://github.com/user-attachments/assets/bd7c5784-da6d-4157-8cc2-e24c5b3e51bd) ![image](https://github.com/user-attachments/assets/44c3c896-dd13-4e23-af68-7facd68654a4) ![image](https://github.com/user-attachments/assets/5512c822-5eb8-4a4f-b19f-361aa0d5cee3) 4. When creating a knowledge base, select Feishu Knowledge Base as the data source (Note: Currently Feishu Knowledge Base only supports docx type documents) ![image](https://github.com/user-attachments/assets/1c9e03a7-46d4-449a-b098-9a6fcf681968) ![image](https://github.com/user-attachments/assets/2ae7e6fa-cd3e-4753-974f-18d159439e3c) ![image](https://github.com/user-attachments/assets/781dcb39-5ac4-457b-878c-bfa20a2e98f9) ![image](https://github.com/user-attachments/assets/de8b7a67-42d4-41aa-add2-ab8bbe5d40b4)
yindo added the pull-request label 2026-02-21 20:39:31 -05:00
yindo closed this issue 2026-02-21 20:39:31 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#26405
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?