Skip to content

docs(channels): explain Feishu webhook path and port limits on shared workspaces - #62

Open
mrgoonie wants to merge 3 commits into
devfrom
claude/dazzling-archimedes-rm0eij
Open

mrgoonie wants to merge 3 commits into
devfrom
claude/dazzling-archimedes-rm0eij

Conversation

@mrgoonie

Copy link
Copy Markdown
Contributor

Summary

This documents the Feishu/Lark webhook rules added in nextlevelbuilder/dewee#1740, which fixes nextlevelbuilder/dewee#1730. The change is in console/channels-and-contacts.md, in both en and vi.

  • On a shared (non-master) workspace, the Webhook Path must sit under /feishu/. A path outside /feishu/, or one that ends in /, falls back to /feishu/events.
  • Two workspaces cannot share a path: only one of them receives the events.
  • Only the master workspace can open a separate Webhook Port. On other workspaces the port is ignored and events arrive on the main address.

The field labels match the dashboard UI strings: "Webhook Path"/"Webhook Port" in en, "Đường dẫn webhook"/"Cổng webhook" in vi.


Generated by Claude Code

… workspaces

Refs nextlevelbuilder/dewee#1730

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FL32ruARdtg8kPnrFS8NVD
Gateway dev now refuses these fields outside the master workspace on
save, so other workspaces use /feishu/events on the main address and
should prefer WebSocket mode on a shared gateway.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FL32ruARdtg8kPnrFS8NVD

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants