Skip to main content
When Integration & Automation processes an app’s data, each connector step determines what happens to that data next. DingTalk currently offers two categories of connector steps:
  • Official connectors
  • Custom connectors

​
FAQ

Q: When using a connector with silent login, can I retrieve images submitted via silent login? Yes. Retrieving silent-login image URLs is built into the connector. Q: Can a leave request submitted through a connector be withdrawn? No. The DingTalk leave-withdrawal API is not yet integrated, so withdrawing leave requests is not supported at this time. Q: Why does testing a connector return “unsafe address!”? Requests to domains on internal networks or containing redirect links are filtered out by security rules. Q: Can a connector pull DingTalk attendance data? Yes — use the Attendance connector under Integration & Automation to sync data with DingTalk attendance. Q: The Contacts [Create User] connector returns an error: Step [Add Contact] execution error: can’t parse argument number: “content”:{“errcode”:40103. When calling the Create User API through a connector to invite a user to join an organization, this response may be returned for reasons including but not limited to:
  • Security rule triggered: if an employee is already verified in Organization A, adding the same employee to Organization B produces the message above. On the Client-side, search for team invitations or open the corresponding invitation in Contacts and handle it accordingly.
  • The invited user has enabled Require verification when a team adds me under DingTalk mobile Client-side > Me > Settings > Privacy > Teams and Members. Once enabled, search for team invitations on the Client-side or open the corresponding invitation in Contacts and handle it accordingly.
After the user accepts and successfully joins the organization, if the organization deletes the user on the same day, calling the API again within 24 hours to invite the same user also returns the error above.
Q: What are the Integration & Automation connector entitlements across YiDA editions? Integration & Automation - Connectors Q: How do I troubleshoot when an integration & automation run returns an error? The run log shows whether the current event flow was triggered successfully. You can quickly filter by execution status and date. If an error occurs, review each step’s configuration to determine whether changes to the form design, card design, or custom connector design are the cause. Trigger type Q: Can a connector integrate with DingTalk attendance? Yes. Call DingTalk attendance capabilities through the Attendance connector under Integration & Automation. To analyze attendance data, this is currently supported only via pulls in Data Preparation, and requires DingTalk Professional edition plus YiDA Premium or YiDA Hybrid Cloud edition. Otherwise, the data cannot be retrieved. Q: Why does integration & automation fail to trigger automatically?
Note: Automatic triggering supports a chain of up to 3 levels. That is, Flow A triggers Flow B, and Flow B triggers Flow C, but Flow C cannot trigger Flow D.
Automatic triggering does not take effect in the following cases:
  1. For OA approvals initiated through integration & automation, an [App event trigger] configured to fire after the OA approval completes does not take effect. In contrast, a manually submitted OA approval can trigger the automation flow.
  2. When data is created through integration & automation or business rules, a [Time-Based Triggers] configured on the target form does not take effect.
  3. When an approval is initiated through integration & automation, a workflow trigger configured on the corresponding workflow form for the [Create] event does not take effect.
  4. When data is created or updated through business association rules, a [form event trigger] configured on the target form does not take effect.
  5. When integration & automation modifies data across apps, the automation flow configured on the target form does not take effect.
Orchestration design Q: How do I retrieve more than 100 records when filtering data?
Note: Only the top 100 records can be retrieved, based on the sorting rules.
Step overview