Help Center/ CodeArts/ User Guide/ Preparations/ Managing Project Notifications/ Setting WeCom Subscriptions
Updated on 2026-01-29 GMT+08:00
View PDF
Share

Setting WeCom Subscriptions

Scenario

When any of the following events occurs, CodeArts sends a message through HTTP to the WeCom group that has subscribed to the event.

Table 1 Event types

Category

Event Type

Repository

Capacity warning

Repo deleted

MR

MR opened

MR updated

MR merged

MR reviewed

MR approved

Review created

Review comment resolved
Table 2 Event types

Event Type

Notification Content

CodeArts Pipeline

Completed
  • Pipeline name
  • Pipeline execution description
  • Executor
  • Trigger
  • Project name
  • Execution time
  • Running status

Failed

Paused

Suspended

Ignored
Table 3 Event types

Event Type

Notification Content

Check task

Completed

  • All
  • Gate check passed
  • Gate check failed
  • Check result
  • Gate check result
  • Number of issues
  • Redirect URL
  • Executor
  • Completion time
Table 4 Event types

Event Type

Notification Content

Build task

Task successful
  • Task name
  • Executor
  • Execution time

Task failed

Task disabled

Task deleted

Task configurations updated
Table 5 Event types

Event Type

Notification Content

Application

Application deployed
  • Application name
  • Execution result
  • Execution ID
  • Executor
  • Execution time
  • Project name

Deploy application failed

Deploy stopped

Constraints

This function is now available in the AP-Singapore region.

Prerequisites

You have created a CodeArts project, and your role in the project is Project Administrator or Project Manager.

Procedure

  1. Go to the CodeArts homepage.

    1. Log in to the CodeArts console, click , and select a region where you have enabled CodeArts.
    2. Click Go to Workspace.

      If your account uses the old billing mode (see Old Billing Modes), click Access Service.

  2. Click the target project name to go to the project.
  3. In the navigation pane, choose Settings > General > Notifications.
  4. Click the WeCom tab.
  5. Configure the parameters and click OK.

    Figure 1 Configuring WeCom notifications (CodeArts Pipeline is used as an example.)
    Table 6 Setting WeCom subscriptions

    Parameter

    Description

    URL

    The webhook URL of your WeCom group robot. Start with http:// or https://. The URL cannot exceed 256 characters.

    For details about how to obtain the webhook URL of your WeCom group robot, see section "How to set group robot" in the WeCom Help Center. (The section name is subject to updates of the WeCom Help Center.)

    Event Types

    Event types that can trigger a WeCom notification. For details about the supported event types, see Scenario.

    Notification Content

    Content of the WeCom notification. For details about the configurable content, see Scenario.

    This parameter is optional. Configure it as needed.

    @user_id

    WeCom user IDs of the members you want to mention. Separate the IDs with semicolons (;). The total IDs cannot exceed 1,000 characters. Digits, letters, semicolons (;), periods (.), hyphens (-), underscores (_), and at signs (@) are supported.

    This parameter is optional. Configure it as needed.

    The updated configuration is displayed.

Parent Topic: Managing Project Notifications