Automated JobsDB Applicant Screening
Every morning, WebRun signs in to your JobsDB employer account, reads applications received since yesterday, checks each against the must-have criteria you listed for the role, drafts a screening-call invite in Gmail for the shortlist, and holds matching interview slots in Google Calendar.
How do I screen new job applications every morning without doing it by hand?
WebRun checks your JobsDB employer account every morning, reads applications received since yesterday, and sorts them against the must-have criteria you set for each role. It drafts a screening-call invite in Gmail for the shortlist, leaves it unsent for your approval, and holds tentative interview slots in Google Calendar.
- Overnight applications are sorted with reasons before your first coffee
- Shortlisted candidates get an invite the same day instead of next week
- No candidate is ever contacted or rejected without a human pressing send
Built for recruiters · hiring managers · HR teams · growing companies in Asia
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
www.jobsdb.comin a real browser with your saved login - no setup, no API keys. -
1
JobsDB - review new applications
jobsdb.com
WebRun opens JobsDB to review new applications. - Sign in to your JobsDB employer account and open each live posting
- List applications received since yesterday with the candidate name and applied date
- Read each application against the must-have criteria you set for the role, such as required skills, years of experience, and work location
- Sort candidates into shortlist, maybe, and not a match
- Note the reason for each shortlist decision so a human can check the reasoning
Done when Every new application is sorted with a written reason for its bucket.
-
2
Gmail - draft the screening invites
gmail.com
WebRun opens Gmail to draft the screening invites. - Draft a short screening-call invite for each shortlisted candidate
- Include the role, the call length, and two or three proposed times
- Keep the tone warm and identical across candidates for the same role
- Leave every message unsent in Drafts. No candidate is contacted without you pressing send
- Draft nothing at all for the maybe and not-a-match buckets
Done when Each shortlisted candidate has an unsent invite waiting in Gmail Drafts.
-
3
Google Calendar - hold interview slots
calendar.google.com
WebRun opens Google Calendar to hold interview slots. - Find open slots in the interview window you keep free each week
- Hold a tentative slot for each proposed time in the drafted invites
- Title each hold with the role and the candidate name
- Send no invitations to the candidate. The hold is on your calendar only
- Release holds automatically if the draft is still unsent after three days
Done when Interview time is held for every shortlisted candidate you may invite.
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 email candidates without me?
No. Every screening invite is left unsent in Gmail Drafts, and the calendar holds are private to you. No candidate hears anything until you read the draft and press send.
Does it reject anyone?
No. WebRun sorts applications into buckets with a written reason and never sends a rejection, never closes an application, and never changes a candidate's status in JobsDB. Every decision stays with a human.
What criteria does it screen on?
Only the must-have requirements you list for the role, such as specific skills, years of experience, and work location. It records the reason for each decision so you can review and override it.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.