Fix WeCom and Feishu group bot webhook failures in Duaer

Read the Duaer node output first

Both bots often answer HTTP 200 on errors, so the Duaer node looks green while nothing is posted. Check errcode (WeCom) or code (Feishu) in the output; anything but 0 failed. To fail loudly, add If on that value not equal to 0, then Stop and Error.

WeCom group bot

• 93000: invalid webhook URL. The bot was removed or the key was cut off; copy the URL again and update the Duaer credential.
• 45009: too fast. Each bot takes up to 20 messages a minute; combine messages, or slow down with Loop Over Items and Wait.
• Too long: text up to 2048 bytes, markdown up to 4096 bytes. Truncate or split.

In Duaer, send with the WeCom node message-push resource and a group-bot Webhook credential. Refer to Send a WeCom message in Duaer.

Feishu custom bot

Duaer posts to a Feishu bot with HTTP Request: Method POST, the webhook URL, Send Body JSON with {"msg_type":"text","content":{"text":{{ JSON.stringify($json.message) }}}}. JSON.stringify keeps quotes and line breaks from breaking the JSON.

• 19024 Key Words Not Found: the bot requires a keyword the message lacks.
• 19021 sign match fail: signature check is on and the signature or timestamp is wrong (timestamp within one hour). Use keyword or IP checks instead if you can.
• 19022 Ip Not Allowed: the IP allowlist is on; add the IP Duaer calls from.
• 9499 Bad Request: the body shape is wrong, usually content sent as a string or a misspelled msg_type.
• 11232: too fast; slow down.