Developer Guide- Achieve seamless data interconnection between YiDA forms. Through the configuration and orchestration of data operation nodes, business users no longer need to write advanced functions or code.
- Connect to DingTalk first-party connectors—including Work Notifications, group notifications, To-Do tasks, Contacts, events, Calendar, attendance, intelligent HR, and daily and monthly reports (manufacturing)—to handle complex scenarios for task processing and message sending.
- Support enterprise development of custom connectors to integrate resources, transfer data, and link business processes between DingTalk YiDA, DingTalk ecosystem apps, and other third-party apps.
Trigger Types
YiDA’s Integration & Automation capability can be viewed as process-based logic orchestration. Any logic flow must be initiated by a trigger. YiDA connectors currently support the following four trigger types:- Form event trigger — Fires on specified form or process events, such as form data submission or process step status updates.
- Time-Based Triggers — Fires cyclically on a set schedule, for example, every Tuesday at 10:00 AM.
- App event trigger — Fires on specified DingTalk first-party, ecosystem, or third-party app events, such as when a new user is added to Contacts.
- Webhook trigger (not yet available) — Fires when a request is received at a specified URL.
Nodes
Because YiDA Integration & Automation is essentially logic orchestration, logic nodes are required. YiDA provides the following node types:- Trigger — Configure the trigger’s execution rules as the starting point of the logic flow. For example, fire when data is successfully submitted in a specific form.
- First-Party Connector — YiDA offers a broad set of first-party connector capabilities. These connectors integrate seamlessly with DingTalk’s native features, such as sending DingTalk messages and creating To-Do tasks.
- Custom Connector — Use the YiDA Connector Factory to build custom connections to in-house systems or third-party app systems. For detailed configuration, see the Create Connector documentation.
- Data Node — Primarily used to create, read, update, and delete YiDA data.
- Create Data — Add one or more records to the target table. Two methods are currently supported: add in form and add in subtable.
- Update Data — Update one or more records in the target table. When no data is retrieved, you can configure the node to be skipped or to add a new record.
- Get Single Record — Retrieve a single record from the target table for further processing (update or delete). Typically placed upstream of update or delete nodes.
- Get Multiple Records — Batch retrieve multiple records from the target table for further processing (update or delete). Typically placed upstream of update or delete nodes.
- Delete Data — Delete data from a specific form.
- Branch Node — Branch nodes support different rule configurations for different conditions and allow multiple conditions to run rule configurations in parallel.
- Conditional Branch — Conditional branches follow a priority order; only the highest-priority branch runs.
- Parallel Branch — Parallel branches have no priority; all branches that meet their conditions run.
- Initiate Approval — Start an approval process.
- Message Node — Send messages, including in-app messages and mail.
- Message Notifications — Send DingTalk Work Notifications or group messages to specified users or roles.
- Send Mail — Send messages to specified email addresses. For email security, the sender’s email account password requires an authorization code.
- Developer Node (Groovy) — Implement code logic through Groovy scripts.