Feishu / Lark
The catalog declares Feishu/Lark long-connection and webhook profiles. The standard setup surfaces create the default Long connection account, which avoids a public webhook. The presence of a webhook or switch action in the catalog does not mean the standard UI exposes a profile selector.
Connection Profiles and Setup Limits
| Profile | Required credentials | Public HTTPS |
|---|---|---|
Default long connection (feishu.websocket.v1) | App ID, App Secret | No |
Webhook (feishu.webhook.v1) | App ID, App Secret, Verification Token, Encrypt Key | Yes |
Use the platform's official overview for the current app console.
Platform Prerequisites
For either profile:
- create an app and enable bot capability;
- grant the required bot messaging permissions; and
- subscribe to message events.
Match platform-side delivery to the existing Anyy profile. Standard new-account setup uses long connection.
Connect
Open Dashboard → Channel → Add and choose Feishu / Lark to configure the default long connection. Enter App ID and App Secret. Direct messages default to pairing; groups default to mention.
Run anyy setup channel in an interactive terminal and choose Feishu to change its CLI policy inputs. The standard CLI, TUI and Dashboard setup consumers do not currently offer a connection-profile selector or switch gesture. Do not treat the catalog's switch descriptors as a working wizard command.
An existing webhook account is updated under its existing profile. Its CLI form includes the webhook credentials; Dashboard/TUI update only the App credentials they expose.
For an existing webhook account, enable the shared listener and HTTPS proxy described in Messaging Platforms, then expose:
/channels/feishu/ACCOUNT_ID/webhook
The default account ID is work. Configure the same Verification Token and Encrypt Key in Feishu/Lark and Anyy.
Access Policies
Direct messages support pairing, open, allowlist, and disabled. Groups support mention, open, allowlist, and disabled. These policy inputs are in the CLI wizard, not the Dashboard credential form. Current setup has no Feishu allowlist-entry editor; consult the shared setup limits before selecting that policy.
anyy channel pairing list
anyy channel pairing approve --request REQUEST_ID
Verify the Connection
anyy channel doctor feishu
anyy channel reload
Test a direct message first, then a group mention.
Troubleshooting
| Problem | Check |
|---|---|
| Long connection never becomes live | App credentials, bot capability, event subscription, outbound network |
| Webhook verification fails | Public HTTPS route, Verification Token, Encrypt Key |
| Events arrive but messages are ignored | DM/group policy, pairing, or mention requirement |
| Reply is unauthorized | Bot messaging permissions and app publication state |
| Need a different connection profile | Current standard setup has no switch selector; do not guess a profile flag or action |