openclaw - 💡(How to fix) Fix [Bug]: Clawdbot cannot receive messages from Feishu (Lark). No message push notifications are received from Feishu [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#50078Fetched 2026-04-08 00:59:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1subscribed ×1

Clawdbot cannot receive messages from Feishu (Lark). No message push notifications are received from Feishu

Root Cause

Clawdbot cannot receive messages from Feishu (Lark). No message push notifications are received from Feishu

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Clawdbot cannot receive messages from Feishu (Lark). No message push notifications are received from Feishu

Steps to reproduce

  1. Configure Feishu channel (set up Feishu bot in openclaw.json)
  2. Start Gateway
  3. Send a message to the bot from Feishu
  4. Clawdbot does not receive/respond to the message

Expected behavior

  • Clawdbot should receive Feishu messages normally
  • Should be able to respond to messages sent by Feishu users

Actual behavior

  • Cannot receive Feishu messages
  • Feishu shows message sent successfully, but Clawdbot has no response

OpenClaw version

  • Clawdbot-CN Version: 2026.2.5 (build 2534359) - Node Version: v22.22.0 - OS: Linux WSL2 (6.6.87.2-microsoft-standard) - Channel: Feishu (Lark)

Operating system

OS: Linux WSL2 (6.6.87.2-microsoft-standard)

Install method

npm

Model

qwen3.5f

Provider / routing chain

openclaw-qwen2.5

Config file / key location

No response

Additional provider/model setup details

  • Feishu app type: [Self-built enterprise app / Third-party app]
  • Callback configuration: [Configured / Not configured]
  • Message encryption: [Enabled / Disabled]

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves configuring the Feishu callback correctly. Here are the steps:

  • Check the Feishu app configuration and ensure the callback URL is set to the Clawdbot Gateway URL.
  • Verify that the Feishu app has the necessary permissions to send messages to the Clawdbot.
  • Update the openclaw.json file with the correct Feishu bot configuration.

Example openclaw.json configuration:

{
  "feishu": {
    "app_id": "YOUR_APP_ID",
    "app_secret": "YOUR_APP_SECRET",
    "callback_url": "https://your-clawdbot-gateway-url.com/feishu/callback"
  }
}
  • Restart the Clawdbot Gateway after updating the configuration.

Verification

To verify the fix, send a message to the Feishu bot and check if the Clawdbot receives and responds to the message. You can also check the Feishu app logs to ensure that the message is being sent successfully.

Extra Tips

  • Ensure that the Feishu app is configured to use the correct encryption method (if enabled).
  • Check the Clawdbot logs for any errors related to the Feishu integration.
  • If issues persist, try resetting the Feishu app configuration and re-configuring the Clawdbot integration.

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…

FAQ

Expected behavior

  • Clawdbot should receive Feishu messages normally
  • Should be able to respond to messages sent by Feishu users

Still need to ship something?

×6

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

Back to top recommendations

TRENDING