notify-channel-copilot

Create a notify channel with ident dingtalk and request_type http, then set the URL to the group robot webhook, Method to POST, and Content-Type to application/json. The message text must contain the keyword configured on the robot, since the built-in provider only supports keyword validation, not signing.

Feishu 9499 Bad Request usually means the request body JSON is invalid, most often caused by backslashes in label values like Windows paths breaking JSON escaping. Wrap label values with jsonMarshal in the body template, for example {{$labels.path | jsonMarshal}}, to produce valid JSON strings.

The test button uses recipients typed into the form, while real alerts resolve sendtos from each user's contact_info field matching the channel's ContactKey. If users lack that contact_info field or the notify_rule selects no users, sendtos is empty and nothing is sent.

The built-in DingTalk and Feishu providers do not natively sign requests with timestamp and sign parameters. Use keyword or IP allowlist validation instead, or route through a script channel that computes the signature before calling the webhook.

Yes, any custom ident works if request_type is one of http, script, smtp, flashduty, or pagerduty. The provider registry falls back by request type, so a custom ident with request_type http is handled by the generic callback provider.

Query the notification_record table for status and error_message, noting the details field truncates at 2048 characters. For the full request and response, set the center log level to debug and grep for 'send http request:' or 'send_http: failed' in n9e-center.log.