Product Introduction

Product Overview

Strengths

Product Features

Use Cases

Purchase Guide

Billing Instructions

Purchase Guide

Upgrade Instructions

Renewal Instructions

Quick Start

Data Access

Creating a VPC Data Source

Creating Cloud Data Sources

Creating Proprietary Data Sources

Data Table Creation and Data Processing

Introduction to Data Analysis Basics

Data Table Creation

Data Processing

Data Analysis

Analysis Settings

Interactive Analysis

Ad-Hoc Analysis

Data Visualization

Public Style Setting Instructions

Filter Components

Chart components

Rich Text Component

Other Components

Mobile Terminal Layout Editor

Theme Settings Introduction

Page Layout Introduction

Dashboard Directory Management

Collaboration and Application

Push Channel Management

Report Push

Sharing

Embedding

Self-Service Data Retrieval

Metric Alarms

Data Security

Parameter Construction

Platform Management

Account and Permission Management

Statistics and Analysis

System Settings

Resource Migration

Practical Tutorial

Collection of Optimization Practices

Performing Trend Analysis

Performing Proportion Analysis

Performing Data Analysis with Excel Files

Creating Tables

API Documentation

History

Introduction

API Category

Making API Requests

Project Management APIs

Role APIs

Database Table APIs

Report Embedding APIs

Page Management APIs

Data Types

Error Codes

FAQs

Relevant Agreements

Service Level Agreement

Data Privacy And Security Agreement

WeCom App Authorization

PDF

Focus Mode

Font Size

Last updated: 2025-09-19 15:24:43

When the user's working environment is WeCom, the user can conveniently push information to the bound WeCom account via the WeCom app push feature. Make sure to complete the API authorization for the app before using the WeCom app push feature.
What is the difference between the WeCom app and WeCom Robot?
1. The WeCom app enables the targeted push of messages to WeCom users (a one-to-one message sending action). The advantage is security and control, but the downside is the potential impact of official policies (which might involve fees).
2. With the WeCom Robot, once a user subscribes to the robot, the user will receive push notifications (similar to subscribing to a broadcast radio station, where the broadcast is not limited to specific subscribers, making it a one-to-many messaging action). The advantage is convenience, while the downside is potential security risks. The WeCom Robot is mainly used for message push in non-sensitive data scenarios.
﻿
This document introduces the following operations:
Obtaining the CopID from the WeCom platform.
Authorizing and activating the WeCom app in BI.
Binding the user's WeCom account.
Viewing push records.
﻿
To use the WeCom app for message push, go to WeCom App Push.
Obtaining the CopID from the WeCom Platform
1. Prerequisite: The WeCom account has been registered, and the administrator's support is needed for the current operation.
2. Go to the WeCom Admin Backend > My Company > Company Information, and find the Company ID (CorpID).
﻿
3. Copy the Company ID for later use.
﻿
Authorizing and Activating the WeCom App in BI
1. Go to the Business Intelligence (BI) console > Toolbox > WeCom app push.
﻿
2. Click Authorize the API to start the authorization process.
﻿
﻿
3. Enter the previously obtained CorpID and submit to complete the API authorization process.
﻿
﻿
Binding the User's WeCom Account
To use the WeCom push, users need to bind their WeCom account.
﻿
1. Go to the WeCom Admin Backend > Contacts.
﻿
Obtain the WeCom account on the details page and copy the account for later use.
﻿
﻿
2. Go to the BI console > Users > the user list > Edit.
﻿
Enter the full WeCom account to search, select the user, and save.
﻿
Viewing Push Records
Go to Push Records to view the results of all WeCom app pushes. Users can filter the records by keywords, including project, status, and title.
﻿
Click View details to check the content sent this time (including the template content).
﻿
Note:
The availability of push channels eventually depends on whether they are supported in the user's located region and compatible with the user's work environment.
﻿