solution channel medium macos linux windows feishu

Feishu: TTS voice replies fail in group chats with error 234001

Work around Feishu group-chat voice send failures (234001 Invalid request param) by avoiding auto-TTS in groups and using DM or tagged TTS until the plugin is patched.

By CoClaw Team •

Symptoms

  • TTS is enabled (Edge / OpenAI / ElevenLabs), and DM voice replies work.
  • In Feishu group chats, the voice send fails with a Feishu API error like:
{ "code": 234001, "msg": "Invalid request param." }

and the gateway logs show a 400 error on the send call.

Cause

Feishu’s message send API uses different identifiers for different destinations:

  • DMs typically route by open_id
  • Group chats route by chat_id

When the sender uses the wrong receive_id_type (or passes the wrong id for a group), Feishu returns 234001 Invalid request param.

As an operator, you usually cannot fix this purely via openclaw.json if the mapping is hardcoded in the Feishu plugin’s send path.

Fix

Until the Feishu plugin is patched, treat this as “voice in groups is unreliable” and use one of these workarounds.

Switch auto-TTS to tagged mode so voice is only generated when you explicitly request it:

{
  messages: {
    tts: {
      auto: "tagged",
    },
  },
}

Then restart the gateway:

openclaw gateway restart

Operational rule: do not use tagged TTS in Feishu groups until the sender bug is fixed. Use it in DMs only.

2) If you need voice, use a DM thread instead of a group

Because DMs and groups have different identifier rules, a DM is often the fastest way to keep voice replies working.

3) Disable TTS entirely (most predictable)

If voice failures are creating user confusion, turn TTS off while you operate in groups:

{
  messages: {
    tts: {
      auto: "off",
    },
  },
}

Verify

  • In a Feishu group chat, trigger a reply that would normally produce TTS.
  • Confirm OpenClaw sends a normal text reply (and does not attempt to send voice).
  • In a DM (optional), confirm tagged TTS works when you explicitly request it.

If you still see 234001, capture:

  • the exact 234001 error block from logs
  • your messages.tts.* config block
  • your channels.feishu.* config block

Verification & references

  • Reviewed by:CoClaw Code Team
  • Last reviewed:March 14, 2026
  • Verified on: macOS · Linux · Windows
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources