Skip to main content
Note: Only DingTalk Organization Admins can operate this connector. To learn how to become a DingTalk Admin, see 👉: Become a DingTalk Admin.

1. Use Case

Use this connector in day-to-day attendance to notify the system when an approval is granted. Currently, only leave requests are supported. For example, if an employee is scheduled to work from 8:00 to 18:00 today and submits a leave request through a YiDA workflow form that the approver approves, calling this connector will notify DingTalk Attendance that the employee does not need to clock in today, will not be marked as absent, and the clock-in status will be shown as On leave.

2. Steps

2.1 Step 1: Create and Configure the Workflow Form

Create a workflow form as the carrier for leave approval, and configure the workflow steps to prepare for calling the connector later.

2.1.1 Create the Workflow Form

Steps:
  1. Create a new form and name it “Leave Request”.
  2. Add two date components, name them “Leave Start Time” and “Leave End Time”, set them as Required, and set the date format to “YYYY-MM-DD HH:mm”. (See Figure 2.1-1.)
Figure 2.1-1 Add and configure the date components
  1. Add a member component, name it “Requester”, set it as Required, set the Default value to Formula edit, and select the formula “USER()” to automatically retrieve the currently signed-in user. (See Figure 2.1-2.)
Figure 2.1-2 Add and configure the member component
  1. Click Save in the upper-right corner of the form.

2.1.2 Workflow Design

Steps:
  1. On the admin backend page, select the “Leave Request” workflow form, click “Workflow” at the top of the page, click Edit, and set the approver to the requester. Click Save, and then click Publish. (See Figure 2.1-3.)
Figure 2.1-3 Workflow design

2.2 Step 2: Create and Configure the Connector

For an introduction to the YiDA connector, see: Integration & Automation - Connector
Step 1 prepared the form required by the attendance connector. Next, configure the connector for the “Leave Request” form so that an approval notification is automatically sent to DingTalk Attendance.

2.2.1 Create the Connector

Steps:
  1. On the edit page of the “Leave Request” form, click “Page Design” at the top, select “Integration & Automation” on the left, and click the “Create Integration & Automation” button. (See Figure 2.2-1.)
Figure 2.2-1 Connector entry point
  1. Name the connector “Attendance”, set the Trigger type to “Form event trigger”, and click Confirm.
(See Figure 2.2-2.) Figure 2.2-3 Create the connector

2.2.2 Configure the Connector

Steps:
  1. Select “Form event trigger”, set the trigger event to “Create Success”, set the data filter to “All data”, and click Save. (See Figure 2.2-4.)
Figure 2.2-4 Configure the form event trigger
  1. Select “Connector”, select the “Attendance” app, and click Next. (See Figure 2.2-5.)
Figure 2.2-5 Select the “Attendance” app
  1. Under Actions, select “Notify Approval Granted” and click Next. (See Figure 2.2-6.)
Figure 2.2-6 Select the action
  1. Configure the action. (See Figure 2.2-7.)
Figure 2.2-7 Configure the action
  1. Click Save in the upper-right corner, and then click Publish.

2.3 Step 3: Submit Form Data

After completing the two steps above, the connector configuration is complete. Now, submit a “Leave Request” workflow approval to trigger the connector and send a notification once the request is approved. (See Figure 2.3-1.) Figure 2.3-1 Submit “Leave Request” workflow form data

3. Result

Desktop: Figure 3-1 Desktop - Leave approval notification result Mobile: Path: DingTalk Workbench >> Attendance >> Statistics >> My Statistics Figure 3-2 Mobile - Leave approval notification result

4. FAQ

4.1 How to Become a DingTalk Organization Admin

Answer: To become a DingTalk Admin, contact the Super Admin who created the organization to set it up. Path: DingTalk Admin Console >> Settings >> Permissions >> Admin Group >> Add Admin Group. (See Figures 4.1-1 and 4.1-2.) Figure 4.1-1 Path for the DingTalk Super Admin to add a Sub Admin Figure 4.1-2 The DingTalk Super Admin edits the admin group