Platform Center

Home / Platform management / Operations center / Notifications / Notification Server

Notification Server

Notification servers are used to provide services for sending notification messages to notification objects on the platform. The platform currently supports the following notification servers:

Enterprise Communication Tool Server: Supports integration with Enterprise WeChat, DingTalk, and Lark built-in applications for personal messaging.
Email Server: Sends notifications via email. For related configurations, refer to the Email Notification Server .
Webhook Type Server: Supports integration with Enterprise WeChat Group Robot, DingTalk Group Robot, Lark Group Robot, or sending WebHooks to your specified server.
Expandable Forwarding Server: When you need to integrate other notification channels, the product supports configuring a forwarding server to send the data you need to receive to external notification channels.

Notes

Only one Enterprise Communication Tool Server can be added.

Add Enterprise Communication Tool Server

Enterprise WeChat

Configure the notification server parameters. After filling in the parameters, switch to the global cluster in Cluster Management > Resource Management and create a resource object.

# Obtain the Enterprise WeChat corpId, corpSecret, and agentId from: https://developer.work.weixin.qq.com/document/path/90665
apiVersion: v1
kind: Secret
type: NotificationServer
metadata:
  labels:
    cpaas.io/notification.server.type: CorpWeChat
    cpaas.io/notification.server.category: Corp
  name: platform-corp-wechat-server
data:
  displayNameZh: 企业微信               # Display name in Chinese, encoded in base64 by default
  displayNameEn: WeChat             # Display name in English, encoded in base64 by default
  corpId:                           # Enterprise ID, encoded in base64 by default
  corpSecret:                       # Application secret, encoded in base64 by default
  agentId:                          # Enterprise application ID, encoded in base64 by default

After creation, update the user’s Enterprise WeChat ID in User Role Management > User Management or the user’s Personal Information on the platform to ensure message reception.

DingTalk

Configure the notification server parameters. After filling in the parameters, switch to the global cluster in Cluster Management > Resource Management and create a resource object.

# Obtain DingTalk appKey, appSecret, and agentId from: https://open-dev.dingtalk.com/fe/app#/corp/app
apiVersion: v1
kind: Secret
type: NotificationServer
metadata:
  labels:
    cpaas.io/notification.server.type: CorpDingTalk
    cpaas.io/notification.server.category: Corp
  name: platform-corp-dingtalk-server
data:
  displayNameZh: 钉钉                 # Display name in Chinese, encoded in base64 by default
  displayNameEn: DingTalk           # Display name in English, encoded in base64 by default
  appKey:                           # Application key, encoded in base64 by default
  appSecret:                        # Application secret, encoded in base64 by default
  agentId:                          # Application agent_id, encoded in base64 by default

After creation, update the user’s DingTalk ID in User Role Management > User Management or the user’s Personal Information on the platform to ensure message reception.

Lark

Configure the notification server parameters. After filling in the parameters, switch to the global cluster in Cluster Management > Resource Management and create a resource object.

# Obtain the Lark appId, appSecret, and appShortId from the official documentation: https://open.feishu.cn/document/ukTMukTMukTM/uYDNz4iN2MjL2QzM
apiVersion: v1
kind: Secret
type: NotificationServer
metadata:
  labels:
    cpaas.io/notification.server.type: CorpLark
    cpaas.io/notification.server.category: Corp
  name: platform-corp-lark-server
data:
  displayNameZh: 飞书                  # Display name in Chinese, encoded in base64 by default
  displayNameEn: Lark              # Display name in English, encoded in base64 by default
  appId:                           # Application ID, encoded in base64 by default
  appSecret:                       # Application secret, encoded in base64 by default
  appShortId:                      # Application short ID, encoded in base64 by default

Update the user’s Lark ID in User Role Management > User Management or Personal Information. Fill in the corresponding Lark ID to ensure that notifications can be sent successfully.

Webhook

Configure the notification server parameters. After filling in the parameters, switch to the global cluster in Cluster Management > Resource Management and create a resource object.

apiVersion: v1
kind: Secret
type: NotificationServer
metadata:
  labels:
    cpaas.io/notification.server.type: Webhook
    cpaas.io/notification.server.category: Webhook
  name: platform-webhook-server
data:
  displayNameZh: Webhook               # Display name in Chinese, encoded in base64 by default
  displayNameEn: Webhook               # Display name in English, encoded in base64 by default
  url:                                # Webhook URL, encoded in base64 by default

Update the webhook URL in User Role Management > User Management or Personal Information. Fill in the corresponding webhook URL to ensure that notifications can be sent successfully.

Expandable Forwarding Server

Configure the notification server parameters. After filling in the parameters, switch to the global cluster in Cluster Management > Resource Management and create a resource object.

apiVersion: v1
kind: Secret
type: NotificationServer
metadata:
  labels:
    cpaas.io/notification.server.type: ForwardingServer
    cpaas.io/notification.server.category: Forwarding
  name: platform-forwarding-server
data:
  displayNameZh: 转发服务器             # Display name in Chinese, encoded in base64 by default
  displayNameEn: Forwarding Server   # Display name in English, encoded in base64 by default
  url:                               # Forwarding server URL, encoded in base64 by default

Update the forwarding server URL in User Role Management > User Management or Personal Information. Fill in the corresponding forwarding server URL to ensure that notifications can be sent successfully.