Automated Taleo Requisition Digests
Every morning, WebRun opens Taleo, counts new applicants and pipeline stage totals for each open requisition, posts a summary digest to Slack, and sends a Telegram alert for any requisition with no recruiter activity in the past week.
How do I get a daily summary of new applicants across all my Taleo requisitions?
WebRun checks Taleo every morning for new applicants and pipeline activity across your open requisitions, posts a per-req summary to Slack, and sends a Telegram alert when a requisition has had no recruiter action in a week. Recruiting teams get one daily read on every opening without logging into Taleo first.
- Every open requisition gets a same-day applicant count
- Recruiters see stalled requisitions within a week instead of a quarter later
- Hiring managers get one Slack digest instead of logging into Taleo
Built for Enterprise recruiting teams · Talent acquisition · HR operations · Hiring managers
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
taleo.netin a real browser with your saved login - no setup, no API keys. -
1
Taleo - tally new applicants by requisition
- Open Taleo and list all open requisitions
- Count new applicants and pipeline stage totals for each
- Note the days since the last recruiter action on each requisition
Done when Every open requisition has a current applicant count and a last-activity date.
-
2
Slack - post the daily digest
WebRun opens Slack to post the daily digest. - Post the requisition counts as a digest in the recruiting channel
- Group by requisition so hiring managers can scan their own openings
- Highlight the requisitions with the most new applicants first
Done when The team has today's requisition digest in Slack.
-
3
Telegram - flag requisitions gone quiet
WebRun opens Telegram to flag requisitions gone quiet. - Check which requisitions have had no recruiter activity in 7 days
- Send a short Telegram alert naming those requisitions
- Leave the follow-up action to the recruiter
Done when Stale requisitions are flagged in Telegram the same day they go quiet.
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
Does it contact candidates directly?
No. WebRun only reads requisition and pipeline data in Taleo and posts internal summaries. It never emails or messages a candidate on its own.
How does it decide a requisition has gone quiet?
It checks the last recruiter action logged in Taleo for each requisition and flags any with none in 7 days, so nothing sits unnoticed.
Can I change how often it checks?
Yes. The morning digest and the stale requisition alert both run on a schedule you set, from every morning to a lighter weekly cadence.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.