Automated Keka Leave Approval Chasing
Every morning, WebRun opens Keka, lists every leave request still awaiting approval, works out how long each has waited and which reporting manager owns it, records the queue in Airtable, and writes HR and each approver their own pending list in Notion so nobody plans around leave they have not been given.
How do I chase managers who have not approved leave requests?
WebRun opens Keka every morning, lists the leave requests still awaiting approval, and works out how long each has waited and which reporting manager owns it. It logs the queue in Airtable and writes each approver their own pending list in Notion, so employees learn their leave is approved before they plan around it.
- Every manager opens Notion to only the requests they owe a decision on
- Requests for leave starting this week are flagged before the leave date passes
- HR sees which approvers repeatedly sit on requests
Built for HR teams · people operations · reporting managers · growing companies
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
keka.comin a real browser with your saved login - no setup, no API keys. -
1
Keka - find leave requests awaiting approval
keka.com
WebRun opens Keka to find leave requests awaiting approval. - Open Keka and filter leave requests to those still awaiting approval
- Capture the employee, leave dates, leave type and the date the request was raised
- Identify the reporting manager who owns each approval
- Work out how many days each request has been pending
- Note the employee's leave balance so an approver sees whether the request is even coverable
Done when Every pending leave request is listed with its approver, age and leave balance.
-
2
Airtable - log the ageing queue
airtable.com
WebRun opens Airtable to log the ageing queue. - Add or update a row per pending request with the employee, manager, dates, type and days waiting
- Mark requests that have aged past your threshold, usually a day or two
- Close out rows for requests approved or rejected since the last run
- Keep a running count of pending requests per manager so repeat offenders are visible
Done when The Airtable queue matches the live pending list in Keka.
-
3
Notion - build each approver's list
notion.so
WebRun opens Notion to build each approver's list. - Write one page per reporting manager listing only the requests they owe a decision on
- Put the oldest request first with the employee, dates and days waiting
- Add an HR view holding every pending request across the company, sorted by age
- Flag any request for leave starting within the week so it does not get approved after the fact
Done when HR and every approver have their own pending list in Notion.
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 or reject leave on a manager's behalf?
No. WebRun only reads the pending queue and reports it. Every approval and rejection stays a human decision inside Keka. It also never emails the employee or the manager on its own.
Where do the chase lists go?
Into your own Notion workspace, one page per reporting manager plus an HR view of everything pending. These are internal pages, so they update on their own each morning.
How long does a request wait before it is chased?
You set the threshold once, usually a day or two. WebRun measures every pending request against it and marks the ones that have aged past it at the top of each manager's list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.