openclaw - 💡(How to fix) Fix [Feishu] message tool returns 'Unknown channel: feishu' - cannot send proactive messages [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59770Fetched 2026-04-08 02:40:45
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Participants
Timeline (top)
commented ×1

The message tool returns Unknown channel: feishu when trying to send proactive messages to Feishu users.

Error Message

  1. Error: Unknown channel: feishu

Root Cause

The message tool returns Unknown channel: feishu when trying to send proactive messages to Feishu users.

RAW_BUFFERClick to expand / collapse

Description

The message tool returns Unknown channel: feishu when trying to send proactive messages to Feishu users.

Steps to Reproduce

  1. Configure Feishu channel with WebSocket connection (working fine for receiving/replying)
  2. Call message tool with ction: send, channel: feishu, arget: <user_open_id>
  3. Error: Unknown channel: feishu

Expected Behavior

The message tool should support eishu as a valid channel, consistent with the documentation which lists feishu as a supported channel.

Environment

  • OpenClaw version: 2026.3.23-2
  • Channel: Feishu (WebSocket mode)
  • OS: Windows 10 x64

Additional Context

Feishu channel works correctly for:

  • Receiving messages ✅
  • Replying in session ✅
  • Feishu plugin tools (doc, wiki, drive) ✅

But does NOT work for:

  • Proactive message sending via message tool ❌
  • Sub-agent completion notifications not delivered to Feishu (internal events from webchat source may not route properly)

extent analysis

TL;DR

The issue may be resolved by checking the channel configuration and ensuring that the Feishu channel is properly registered and supported by the message tool.

Guidance

  • Verify that the Feishu channel is correctly configured and enabled for proactive message sending, as it works fine for receiving and replying.
  • Check the documentation and code for any specific requirements or restrictions on using the Feishu channel with the message tool.
  • Investigate the difference in behavior between receiving/replying and proactive sending to identify potential issues with the channel setup or message tool implementation.
  • Review the OpenClaw version and Feishu plugin tools to ensure compatibility and proper integration.

Example

No code snippet is provided as the issue does not contain sufficient code-related information.

Notes

The issue may be specific to the OpenClaw version or Feishu channel implementation, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check and update the channel configuration to ensure that Feishu is properly registered and supported by the message tool, as it is listed as a supported channel in the documentation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING