Integration & Automation - Connectors

The Yida platform is not a closed system. Through connectors, Yida natively supports connectivity with external systems. Currently, Yida has integrated the DingTalk connector, allowing developers to easily integrate official DingTalk applications, applications within the DingTalk ecosystem, and enterprise's own systems into Yida. With Yida connectors, we can achieve the following functions (for detailed usage of connector functions, see the official documentation):

• Easily achieve data interconnectivity between Yida forms. Through configuration and orchestration of data operation nodes, business personnel no longer need to write advanced functions and code;
• Yida integrates with DingTalk's first-party connectors, including work notifications, group notifications, pending tasks, address book, schedule, calendar, attendance, smart personnel, daily/monthly settlements (manufacturing), etc., to achieve complex scenarios for task processing and message sending;
• Support enterprise development of custom connectors to achieve resource integration, data transfer, and business coordination between DingTalk Yida, DingTalk ecosystem applications, and other third-party applications;

Trigger Types

The integration & automation capabilities provided by Yida can be understood as a process-based logical orchestration capability. Logic needs to be triggered by triggers for execution. Currently, Yida connectors support the following 4 trigger types:

• Form Event Trigger - Triggered by specified form or process events, such as form data submission, process node status updates, etc.;
• Scheduled Trigger - Triggered cyclically according to the set time period, such as every Tuesday at 10:00 AM;
• Application Event Trigger - Triggered by specified DingTalk first-party, ecosystem, or third-party application events, such as triggering when adding new members to the address book;
• Webhook Trigger (not yet open) - Triggered when receiving requests from specified URLs;

Nodes

As mentioned above, Yida's integration & automation is essentially logical orchestration, so we need existing logical nodes. Yida provides the following node types:

• Trigger - Used to configure trigger execution rules, serving as the starting point of the logical process, for example, can be configured to trigger when XX form data submission is successful;
• First-party Connector - Yida provides a large number of first-party connector capabilities. Through these connectors, it is easy to connect with DingTalk's first-party capabilities, such as sending DingTalk messages, creating pending tasks, etc.;
• Custom Connector - Customize connections to self-built systems or third-party application systems through Yida connector factory. For detailed configuration, refer to New Connector Documentation
• Data Node - Mainly used for add, delete, modify, and query operations on Yida data;
  • Add Data - Add one/multiple records to the target form. Currently there are 2 ways to add: add in form, add in sub-form;
  • Update Data - Update data in one/multiple target forms. When no data is retrieved, you can choose to skip this node or add a new record;
  • Get Single Record - Retrieve a single record from the target form, then process the data (update, delete), usually upstream of update or delete nodes;
  • Get Multiple Records - Batch retrieve multiple records from the target form, then process the data (update, delete), usually upstream of update or delete nodes;
  • Delete Data - Delete data from a specific form;
• Branch Node - Branch nodes can execute different rule configurations under different conditions, and execute rule configurations simultaneously when multiple conditions are met;
  • Conditional Branch - Conditional branches have priority levels, only executing the branch with the highest priority;
  • Parallel Branch - Parallel branches have no priority levels, and all branches that meet the conditions will be executed;
• Initiate Approval - Used to initiate an approval process;
• Message Node - Used to execute message sending, including both messages and emails;
  • Message Notification - Supports sending DingTalk work notifications or group messages to specified members or roles;
  • Send Email - Send messages to specified email addresses. Considering email security, the sender's email account password needs to be set with an authorization code;
• Developer Node (Groovy) - Implement code logic through Groovy scripts;

Process Orchestration Designer

Yida provides a process orchestration designer for connector logical orchestration. The usage is basically the same as the process designer, as shown below:

Function Demo