---
Title: Integrate events
URL Source: https://company-skill.com/p/eb/eb-integrate-events
Language: en
Description: You want to either (1) capture database changes (like new rows in MySQL/PostgreSQL) and trigger downstream actions, or (2) send/receive events from collaboration tools like DingTalk or Lark using…
---

# Integrate events

Part of **EventBridge**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to either (1) capture database changes (like new rows in MySQL/PostgreSQL) and trigger downstream actions, or (2) send/receive events from collaboration tools like DingTalk or Lark using webhooks — without writing code if possible.

**Typical User Questions**:
- HTTP API
- How to push events to Lark or WeCom?
- Can I trigger Jenkins builds with EventBridge?

## Decision Tree

Pick the best path for your situation:

- **If** your goal is to capture row-level changes (INSERT/UPDATE/DELETE) from **MySQL or PostgreSQL** using **change data capture** → Use API CDC (go to *eb/eb-event-integration*)
- **If** you need to send or receive events from **DingTalk, Lark**, or other **Partner Event Sources** using a **webhook URL** and **HTTP/HTTPS Trigger** → Use (go to *eb/eb-event-integration*)
- **Otherwise (default)** → Start with **** — it’s low-complexity, requires no code, and covers common notification use cases like “new employee joins DingTalk”.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| API CDC | MySQL/PostgreSQL | high | Yes | Yes | Billing: ¥0.0001/request; MySQL gets 10,000 free requests/month, PostgreSQL only 1,000 | `eb/api/eb-event-integration` |
| Webhook | low | No | No | Billing: ¥0.0001 per 1,000 events; DingTalk scenarios include 100 free events | `eb/guide/eb-event-integration` |

## Path Details

### Path 1: API CDC 

**Best For**: MySQL/PostgreSQL 

**Brief Description**: EventBridge provides a synchronous REST API to configure MySQL or PostgreSQL as a **change data capture** event source. You make a single POST request with database connection details (HostName, Port, User, Password) and receive immediate validation. Authentication uses a **Bearer Token** in the Authorization header. This method supports VPC-connected databases via PrivateNetwork.

**Key technical facts**:
- Billing: CDC ¥0.0001/MySQL/ 10,000 PostgreSQL CDC 1,000 
- Auth method: Bearer Token via Authorization header
- Regions available: cn-hangzhou, cn-shanghai, cn-beijing, ap-southeast-1

**When to Use**:
- MySQL/PostgreSQL INSERT/UPDATE/DELETE

- VPC PrivateNetwork 

**When NOT to Use**:
- API HTTP 

**Known Limitations**:
- Only MySQL and PostgreSQL are supported as CDC data sources; other databases are not supported
- PostgreSQL CDC free quota is only 1,000 requests/month, much lower than MySQL's 10,000
- Database connection parameters (HostName, Port, User, Password) must be manually provided in the API request; no auto-discovery mechanism exists
- Configuration is not asynchronous; all parameters must be provided in a single request and validated immediately

### Path 2: 通过控制台集成钉钉、飞书等应用

**Best For**: Webhook

**Brief Description**: Using the EventBridge console, you create a **Custom Event Bus**, define **Event Rules**, and use **Add Target > HTTPS** to route events to a **webhook URL** (e.g., from DingTalk or Lark). The workflow includes options like **Skip Subsequent Steps** and supports **Event Tracing**. This path leverages **Partner Event Sources** for pre-integrated apps and requires only Console SSO authentication. It uses **HTTP/HTTPS Trigger** to deliver events to external endpoints.

**Key technical facts**:
- Billing: ¥0.0001/1000 100 
- Auth method: Console SSO
- Prerequisites: webhook URLEventBridge HTTPS

- webhook GitHub push Function Compute SMQ

**When NOT to Use**:
- CDC webhook

**Known Limitations**:
- Only predefined partner applications (such as DingTalk, Lark, GitHub) are supported; arbitrary HTTP event sources cannot be configured
- Event rules cannot be modified to change the event bus or event source type after creation
- An empty event pattern matches all events, which may cause unintended triggers
- All configuration must be done manually in the console; scripting or automation is not supported

## FAQ

Q: Which path should I start with?
A: If you're integrating DingTalk, Lark, or similar collaboration tools, start with the console path (****). Only choose the API path if you specifically need **change data capture** from MySQL or PostgreSQL.

Q: What if I need to capture PostgreSQL changes but chose the console path?
A: You’ll hit a dead end — the console path only supports **Partner Event Sources** like DingTalk and cannot ingest database change events. You must use the API path with **Bearer Token** authentication and logical replication enabled.

Q: What if I have a custom SaaS app (not DingTalk/Lark) and used the console path?
A: You’ll find that **Add Target > HTTPS** works for *sending* events, but you cannot *receive* arbitrary webhook events unless your app is in the official **Partner Event Sources** list. For custom inbound webhooks, consider Function Compute with API Gateway instead.

Q: Why does PostgreSQL CDC have fewer free requests than MySQL?
A: According to billing facts, PostgreSQL CDC offers only 1,000 free requests/month vs. 10,000 for MySQL — likely due to higher resource usage from logical decoding. Monitor usage if scaling.

Q: Can I automate the console-based integration later?
A: No — the console path is not **automation friendly**. All steps (creating **Custom Event Bus**, **Event Rules**, etc.) must be done manually. If you anticipate needing infrastructure-as-code, start with the API path even for simple use cases.

Q: What happens if I leave the event pattern empty in the console?
A: An empty pattern matches **all events**, which may cause unintended triggers (e.g., sending test events to production DingTalk groups). Always define explicit filters in **Event Rules**.

Q: Do I need to expose my database publicly for CDC?
A: No — for VPC databases, provide **VpcId**, **VSwitchIds**, and **SecurityGroupId** in the API request. The connection uses Alibaba Cloud’s private network, not public internet.

Q: What if I want to integrate a third-party app like GitHub but selected the API CDC path?
A: You’ll find that the API CDC path is designed exclusively for MySQL and PostgreSQL change data capture and does not support webhook-style events from applications like GitHub. You must use the console path with **Partner Event Sources**.

Q: What if I have no coding ability but selected the API CDC path?
A: You’ll struggle because the API CDC path requires managing HTTP requests, Bearer Tokens, and manual database connection parameters. The console path is better suited for non-developers.

## Related queries

integrate external services via events, send events to DingTalk, push events to Lark, trigger HTTP API on new employee, webhook integration, EventBridge third-party integration, connect DingTalk robot, send notification to Lark, how to integrate webhook, can I use EventBridge with WeCom, activate Ev

---
Part of [EventBridge](https://company-skill.com/p/eb.md) · https://company-skill.com/llms.txt