📝 docs: spilit feishu with lark and update overview#13165
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@canisminor1990 @tjx666 - This is a documentation PR (splitting feishu/lark docs and updating overview). Please take a look. |
|
❤️ Great PR @rdmclin2 ❤️ The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d54653043b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ### Configure the Request URL | ||
|
|
||
| Paste the **Event Subscription URL** you copied from LobeHub into the **Request URL** field. The platform will verify the endpoint automatically. |
There was a problem hiding this comment.
Remove the Lark webhook setup until the route is wired
For any user following the new Lark guide, Step 4 cannot complete: BotMessageRouter.handleWebhook() routes /lark/... requests through chatBot.webhooks.lark, but src/server/services/bot/platforms/feishu/client.ts:createAdapter() still registers only a feishu webhook key. That makes Lark's Request URL verification and every later inbound message return 404, so this page currently documents a channel flow that cannot receive webhooks at all.
Useful? React with 👍 / 👎.
| ## Step 6: Test the Connection | ||
|
|
||
| Back in LobeHub's channel settings, click **Test Connection** to verify the credentials. Then find your bot in Lark by searching its name and send it a message to confirm it responds. |
There was a problem hiding this comment.
Validate Lark credentials against the Lark host
For Lark apps, the Test Connection step here will reject valid credentials because FeishuClientFactory.validateCredentials() ignores the selected platform and always instantiates LarkApiClient with the Feishu domain in src/server/services/bot/platforms/feishu/client.ts. As written, this guide sends Lark users through a verification flow that authenticates against the wrong API endpoint.
Useful? React with 👍 / 👎.
💻 Change Type
🔗 Related Issue
🔀 Description of Change
🧪 How to Test
📸 Screenshots / Videos
📝 Additional Information