Feishu Universal Plugin

Feishu Universal is a full OpenClaw channel plugin that provides:

• A real feishu channel integration (gateway, outbound, onboarding, directory, reactions).
• Full Feishu/Lark OpenAPI access through SDK passthrough tools.
• Domain-specific skill packs under skills/.
• Automatic object sharing and notification behavior for docs and knowledge assets.

Channel Identity

• Channel ID: feishu
• Package: @openclaw/feishu-universal
• Plugin ID: feishu-universal
• Manifest file: openclaw.plugin.json

Capability Summary

Channel Runtime

• Inbound monitoring via Feishu event/gateway flow.
• Outbound message delivery (text/media) through channel adapters.
• Account routing for single-account and multi-account deployments.

Tooling Surface

Core utility tools:

• feishu_accounts
• feishu_access_token
• feishu_sdk_request
• feishu_openapi
• feishu_openapi_multipart

Operational tools:

• feishu_bot_info
• feishu_contacts_list
• feishu_chats_list
• feishu_message_send
• feishu_smoke_test

Domain tools:

• feishu_doc
• feishu_app_scopes
• feishu_wiki
• feishu_drive
• feishu_bitable_*

Auto Distribution Behavior

Auto Share on Create

When these operations succeed, the plugin attempts to share the created object to all visible contacts from contact.user.list:

• feishu_doc with action: "create" (object type: docx)
• feishu_bitable_create_app (object type: bitable)
• feishu_drive with action: "create_folder" (object type: folder)
• feishu_wiki with action: "create" when returned object type is shareable

Create responses include auto_share with counters such as shared, skipped, and failed.

Auto Notify on Doc Create

For feishu_doc with action: "create", the plugin also sends the document link as a text notification to all visible contacts.

• Response field: auto_notify
• Key counters: sent, failed

Meeting Schedule Broadcast

For feishu_doc with action: "write" or action: "append", if the title/content matches meeting schedule semantics (Chinese or English meeting keywords), the plugin broadcasts schedule text plus doc link to all visible contacts.

• Response field: meeting_broadcast
• Key counters: sent, failed

Skill Packs

Skill definitions are under skills/ and grouped by SDK domain.

• feishu-sdk-foundation
• feishu-sdk-im-bot
• feishu-sdk-docs-drive
• feishu-sdk-collab
• feishu-sdk-org-security
• feishu-sdk-hr-talent
• feishu-sdk-finance-project
• feishu-sdk-ai-search-content
• feishu-sdk-industry-ecosystem

Namespace mapping reference: skills/NAMESPACE_COVERAGE.md.

Configuration Contract

Primary channel config path:

• channels.feishu

Single Account

channels:
  feishu:
    enabled: true
    appId: "cli_xxx"
    appSecret: "xxx"
    domain: "feishu" # feishu | lark | https://custom-domain

Multi Account

channels:
  feishu:
    enabled: true
    accounts:
      default:
        enabled: true
        appId: "cli_default"
        appSecret: "secret_default"
        domain: "feishu"
      intl:
        enabled: true
        appId: "cli_intl"
        appSecret: "secret_intl"
        domain: "lark"

Legacy aliases for universal API tools are still accepted:

• channels.feishuUniversal
• channels.feishu_universal
• channels["feishu-universal"]

OpenClaw Usage

Common operational commands:

openclaw plugins list --json
openclaw plugins enable feishu-universal
openclaw doctor --fix
openclaw gateway restart

Health and quick checks:

openclaw agent --session-id main --message "Run a Feishu connectivity smoke test and return accountId/domain/results." --json

Troubleshooting

• 404 on contact/chat endpoints: bot visibility, installation scope, or endpoint/resource mismatch.
• 403 on mutation endpoints: missing tenant/user scopes or missing object-level permission.
• Empty wiki spaces: add the bot as a member in each target wiki space.
• Multi-account misrouting: pass explicit accountId in tool calls.

Development and Publish Checklist

1. Update package metadata in package.json.
2. Run npm install.
3. Run npm run typecheck.
4. Run npm pack --dry-run.
5. Publish with npm publish --access public (or your private registry policy).