Automated WeCom Attendance Exception Reports
Every morning, WebRun opens WeCom, reads yesterday's punch records for missing or irregular entries, lists the leave and overtime requests still waiting on an approver, posts the exceptions grouped by department to Slack, and cards each unresolved item in Trello so payroll is not blocked.
How do I clear attendance exceptions before payroll closes?
WebRun clears your attendance exceptions every morning. It reads WeCom punch records for missing or irregular entries, lists leave and overtime requests still waiting on an approver, posts them by department to Slack, and cards each unresolved item in Trello ahead of the payroll cutoff.
- Missing punches are chased daily instead of on payroll day
- Every waiting approval names the approver holding it up
- Nothing that would block the cutoff reaches it unnoticed
Built for HR teams · payroll administrators · operations managers · department heads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
work.weixin.qq.comin a real browser with your saved login - no setup, no API keys. -
1
WeCom - read punches and pending approvals
WebRun opens WeCom to read punches and pending approvals. - Open WeCom and go to the attendance area for your organization
- Read yesterday's punch records and pick out missing, late, or incomplete entries
- List leave applications and overtime requests still waiting on an approver, with who they sit with
- Note the department for every person on the list and how long each item has been open
- Never approve, reject, or amend a record. WebRun only reads and reports
Done when Yesterday's punch exceptions and every waiting approval are captured by department.
-
2
Slack - post exceptions by department
WebRun opens Slack to post exceptions by department. - Post this morning's attendance exceptions to your HR channel in Slack
- Group by department, with the count of unresolved punches and waiting approvals on each
- Name the approver holding each request and how many days it has been sitting
- Flag anything that would block the payroll cutoff if it is not cleared this week
Done when HR has this morning's exception list in Slack, grouped by department.
-
3
Trello - card each unresolved item
WebRun opens Trello to card each unresolved item. - Open your HR board in Trello and add a card per unresolved exception
- Put the person, the date, the exception type, and the approver on the card
- Set a due date ahead of the payroll cutoff on anything that would block it
- Close cards for items that were resolved since yesterday's run
Done when Every unresolved exception has a Trello card with an owner and a due date.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it approve leave or fix a punch record?
No. WebRun reads the attendance data and reports the exceptions. Approving leave, granting overtime, or correcting a punch stays with the approver, so no payroll-affecting record is changed automatically.
Does it message employees about their punches?
No. The Slack post goes to your HR channel and the cards sit on your internal Trello board. Nobody is messaged in WeCom about a missing punch, so the conversation stays with HR.
How does it know what will block payroll?
From the payroll cutoff date you give it. Any unresolved punch or waiting approval that falls in the period being paid is flagged in Slack and gets a Trello due date ahead of the cutoff.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.