When a new employee joins your DingTalk team, you may need to sync that data to internal systems such as HR platforms, access provisioning tools, or notification services. EventBridge connects DingTalk to a custom HTTP API through a serverless pipeline, so new-member events flow automatically to your business endpoint without writing any code.
How it works
The integration connects four components in sequence:
DingTalk detects a new member joining your team.
The DingTalk connector forwards the event to an EventBridge webhook.
EventBridge receives the event on a custom event bus and routes it through an event rule.
The event rule triggers a Function Compute function that calls your HTTP API.
Prerequisites
Before you begin, make sure that you have:
A DingTalk account with a DingTalk team where you are the administrator. For details, see How to create an organization
Step 1: Create a custom event bus
Create a custom event bus with an HTTPS event source. The event source generates a webhook URL that you use in Step 2 to connect DingTalk.
Log in to the EventBridge console and select a region in the top menu bar.
In the left-side navigation pane, click Event Buses. In the Custom Event Buses section, click Quick Create.
In the Create Custom Event Bus panel, complete the following tabs:
Bus: Enter a Custom Event Bus Name and Description, then click Next.
Event Source: Enter an Event Source Name and Description, configure the following parameters, then click Next.
Parameter Value Event Provider HTTP/HTTPS Trigger Request Type HTTPS Request Method POST Security Configuration No configuration required Rule: Click Skip. In the Create Custom Event Bus Directly dialog box, click Confirm.
This creates the event bus without an event rule or event target. You add those in Step 4.
After creation, locate the event source in the list and click Details. Copy the Public Request URL. This is the webhook address for the DingTalk connector.
Step 2: Create a DingTalk connection stream
Set up a connection stream in DingTalk that forwards new-member events to the EventBridge webhook URL from Step 1.
Log in to the DingTalk Open Platform.
In the left-side navigation pane, choose My Connection Streams.
Click New and select Business Stream.
In the Create Stream dialog box, enter a name and description for the business stream. Set Trigger to the new member event trigger.
On the Connection Stream tab, click the add icon, then click Network Request.
In the Network Request panel, configure the following parameters, then click Save.
Parameter Description Example Request Method Must match the method configured in Step 1. POST Request URL The Public Request URL copied from Step 1. https://115964845466****.eventbridge.cn-hangzhou.aliyuncs.com/webhook/putEvents?token=8a5c4e6****Body The fields contained in the message body. root
Step 3: Set up a Function Compute function
Create a service and function in Function Compute to receive events from EventBridge and call your HTTP API.
Create a service
Log in to the Function Compute console. In the left-side navigation pane, click Services & Functions.
Select a region in the top navigation bar. On the Services page, click Create Service.
In the Create Service panel, enter a service name and description, configure advanced options as needed, then click OK.
Advanced service configuration
Parameter Description Log Feature Enable to save function execution logs to Simple Log Service for debugging and analytics. Disable to skip log persistence. Tracing Analysis Feature Enable to upload trace information through Jaeger for performance analysis. See Introduction to Tracing Analysis. Service Role The role that grants functions the required permissions. See Grant Function Compute permissions to access other Alibaba Cloud services. Allow Access To VPC Set to Yes to allow the function to access resources in a Virtual Private Cloud (VPC). Then select or create a VPC, VSwitch, and Security Group. See Configure a network. Allow Function To Access The Internet Set to Yes to allow the function to access the internet. ImportantDisable this setting when using a static public IP address. See Configure a static public IP address.
Create a function
On the Services page, click the service name, then click Create Function.
On the Create Function page, configure the following settings:
In Basic Settings, enter a function name and set Handler Type to Process HTTP Requests.
In Function Code, set Runtime to Node.js, set Code Upload Method to Use Sample Code, and select API Gateway Trigger Function.
Click Create. The Function Details page opens.
Step 4: Create an event rule
Connect the event bus to the Function Compute function by creating an event rule.
In the EventBridge console, open the custom event bus created in Step 1.
In the left-side navigation pane, click Event Rules, then click Create Rule.
In the Create Rule panel, complete the following tabs:
Configure Basic Information: Enter a Name and Description, then click Next.
Configure Event Pattern: Set Event Source Type to Custom Event Source and Event Source to the event source created in Step 1, then click Next.
Configure Event Target: Configure the following parameters, then click Create.
Parameter Description Example Service Type The target service type. Function Compute Service The service created in Step 3. testserver Function The function created in Step 3. testfunction Event The event delivery mode. Complete Event Execution Method The invocation mode for the function. Sync
Step 5: Test the end-to-end flow
Trigger the pipeline by adding a new member to your DingTalk team, then verify that the event reaches Function Compute.
Trigger the event
Invite a new member to join your DingTalk team. For details, see How to add organization members.
Verify event delivery
In the EventBridge console, open the custom event bus from Step 1 and click Event Trace.
Set a time range and click Query.
In the Operation column, click Event Trace to confirm the event was delivered.
Verify function execution
In the Function Compute console, open the function created in Step 3.
Click the Function Logs tab to view the execution logs.
The logs show the incoming event payload from DingTalk, confirming that the function received and processed the new-member event.
Clean up resources
If you no longer need the resources created in this tutorial, delete them to avoid ongoing charges:
EventBridge: Delete the event rule, event source, and custom event bus.
Function Compute: Delete the function and service.
DingTalk: Delete the connection stream from the DingTalk Open Platform.
What's next
Customize the function code to parse the DingTalk event payload and call your business HTTP API with the employee data.
Add error handling and retry logic for production use.
Enable Simple Log Service to monitor event delivery and function execution.