This document uses specific examples to demonstrate the strong security, high availability, and lightweight application-to-application data interconnection scenario built by DingTalk open platform based on Alibaba Cloud Function Compute and EventBridge. It helps official DingTalk applications, third-party applications, and enterprise-owned systems to implement event-driven data flow.

What is DingTalk connector?

DingTalk application center covers many mini programs or H5 applications developed by independent software developers (ISVs). To better intercommunicate with other applications or internal systems of enterprises, a set of event-driven standard data models is required to solve the problems of customer application interconnection and business automation. Therefore, DingTalk connector came into being.

Case studies

Currently, the DingTalk ISVs that use the DingTalk connector are as follows. More ISVs are being docked. Welcome to try them out.

xbongbongcrm

Take the Xbongbong CRM (the leading domestic enterprise mobile SaaS service provider) as an example. The end user of the Xbongbong CRM needs to synchronize the newly entered data such as customer changes, product changes, and contract changes to another SaaS application BOSS accounting (Intelligent Finance Software). In this scenario, Xbongbong CRM is the trigger application, BOSS accounting is the execution application, and customer changes, product changes, contract changes, and other behaviors are trigger events.

Connectors are created by ISV application data providers. In this example, the provider is Xbongbong CRM. Xbongbong CRM sends its data to the connector, which is EventBridge. Enterprise users can create a connection (which is the rule of EventBridge) under this connector to synchronize the data from Xbongbong CRM. Where exactly is the data synchronized? You can configure the execution action (that is, the EventBridge target) in the connection. The execution action here is the event receiving service for BOSS accounting. DingTalk ISV can register its execution actions on the platform in advance, or host the execution actions in Function Compute and connect them to the EventBridge through an HTTP trigger.

In an example scenario where Xbongbong CRM sends data to BOSS accounting, the customer and order data sent by Xbongbong CRM and the customer and order data received by BOSS accounting adopt the same set of customer data model and order contract data model. Xbongbong CRM calls the connector event sending interface. The connector synchronously converts the customer and order data into standard CloudEvents protocol data. This way, BOSS accounting only needs to complete simple format intercommunication when connecting data.

The principle of Eventbridge is described as follows:eventbridge

Configure Function Compute to execute an action

Currently, DingTalk officially supports selling popular templates such as Xbongbong CRM, BOSS accounting, Douyuyun, Ekuaibao, Youcheng finance, Jinzhi CRM, and Antbim. Trigger events include customer change, product change, contract change, and EKB-trigger. Third-party service providers can access the DingTalk cloud applications through the platform based on the primary data standards. The access platform provides data conversion tools, which reduces the costs of registering service providers and using primary data.

Function Compute can be used as the execution action background service of self-built connectors, third-party connectors, and network applications. It can quickly help DingTalk the ISV service providers to build data conversion links for popular Unicom applications, and even does not need to maintain any basic resources. It only needs to interconnect data format and higher-level custom business logic.

To grant permissions to users, perform the following operations:

  1. Log on to the DingTalk open platform.
  2. Create applications.
    Before developing internal applications, you must create an internal application and complete the basic configurations.
  3. Create a self-built connector.
    The connector is for the enterprise to use, and the corresponding data model and execution actions are optional to be configured, such as Xbongbong CRM customer change and other events.
  4. Create custom application connection.
    An application connection consists of application trigger and application execution. The triggered application can be a self-built application or a third-party application that has been created. The execution application can be a self-built application, a third-party application, an enterprise internal application, or a robot. Enterprises can combine different triggered applications and executed applications to interconnect applications in different scenarios.

Configure Function Compute as the connector destination address

At present, Function Compute has been used to sell popular templates such as Xbongbong CRM, BOSS accounting, Douyuyun, Ekuaibao, Youcheng finance, Jinzhi CRM, and Antbim etc. It can also be used as an event trigger target address of custom connectors to host the background code of DingTalk ISV service providers, thus realizing the automation and standardization of the whole process.

Debug DingTalk connector

The ISV service providers convert data sending to EventBridge events, use the CloudEvents protocol to transfer data, and actively trigger the execution of target functions.

For more information, see connector event sending.