How to Use Alibaba Cloud EventBridge HTTP Source for Seamless SaaS Integration

Introduction

Event‑Driven Architecture (EDA) decouples systems by using events. Major companies such as Uber, Deliveroo and Monzo have adopted EDA since 2017. Alibaba Cloud launched EventBridge, a serverless event bus that follows the CloudEvents 1.0 specification, enabling low‑code or no‑code integration of Alibaba Cloud services.

HTTP Source Overview

EventBridge offers an HTTP Source that exposes a webhook URL. It accepts HTTP/HTTPS requests from any network (public or VPC) and converts them into CloudEvents. The service supports configurable security: allowed HTTP methods, source IP ranges, and referer domains.

When a request arrives, EventBridge maps the request headers and body into CloudEvent fields, then users can filter or transform the event in rules before delivering to targets.

SaaS Integration Best Practices

The guide demonstrates three practical integrations using the HTTP Source: DingTalk + GitHub, Grafana alerts, and asynchronous monitoring across multiple clouds.

1. DingTalk monitoring of GitHub push events

Steps:

Create a DingTalk custom robot and enable the “signature” security option.

Create EventBridge resources: an event bus, an HTTP Source event source, a rule, and a DingTalk target.

Create a custom event bus.

Configure a GitHub webhook that points to the HTTP Source URL, set content type to application/json, and select “Just the push event”.

Push code changes to the repository.

Receive a formatted message in the DingTalk group.

Message template (JSON) used for DingTalk:

{"msgtype":"text","text":{"content":"Github push event is triggered. repository: ${repo}, git reference: ${branch}, pusher: ${pusher}."}}

Variable mapping:

{"repo":"$.data.body.repository.full_name","branch":"$.data.body.ref","pusher":"$.data.body.pusher.name"}

2. Grafana alert integration

Create an MNS queue, set up EventBridge resources, and add a Grafana webhook notification channel that points to the HTTP Source URL. Test the webhook; Grafana will POST alerts to EventBridge, which forwards them to the MNS queue for asynchronous consumption.

3. Asynchronous consumption of monitoring alerts

Using HTTP Source, alerts from various monitoring tools (Grafana, Zabbix, Nagios, etc.) and cloud providers can be unified into EventBridge, then consumed by downstream services such as MNS queues.

More Integrations

HTTP Source also supports third‑party services including Prometheus, SkyWalking, Open‑Falcon, Cacti, Dynatrace, Salesforce, Shopify, Gitee, and others via simple webhook configuration.

Conclusion

EventBridge’s HTTP Source extends the serverless event bus with a webhook‑based entry point, allowing SaaS and multi‑cloud services to integrate without code changes. Open APIs and multi‑language SDKs further simplify custom integrations.

Related Links

DingTalk custom robot documentation: https://open.dingtalk.com/document/group/custom-robot-access

Grafana documentation: https://grafana.com/docs/