Automated TazWorks Pending Order Digest
Every morning, WebRun opens TazWorks, pulls every order that is not yet complete, logs each one to a Google Sheet grouped by status and days open, and posts your team a short Slack digest of what's still pending.
How do I get a daily summary of pending background check orders?
WebRun opens TazWorks every morning, pulls every order that is not yet complete, and logs each one to a Google Sheet with its status, days open, and assigned researcher. It then posts your team a short Slack digest grouped by stage with the oldest orders called out, so nothing pending gets forgotten between morning check-ins.
- Every pending order is visible in one place each morning
- Aging orders get called out before they become a client complaint
- No status update requires manually opening TazWorks
Built for CRA operations teams · screening coordinators · background screening companies · ops 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
www.tazworks.comin a real browser with your saved login - no setup, no API keys. -
1
TazWorks - pull every pending order
tazworks.com
WebRun opens TazWorks to pull every pending order. - Open TazWorks and filter the order queue to anything not yet complete
- Capture each order's applicant, package type, current step, and days open
- Group orders by status: awaiting verification, awaiting county search, in QC
Done when Every pending order is captured with its current step and days open.
-
2
Google Sheets - log status and days open
google.com
WebRun opens Google Sheets to log status and days open. - Log each pending order as a row with status, days open, and assigned researcher
- Update existing rows rather than duplicating an order already logged
- Highlight orders open longer than your target turnaround
Done when The pending-orders sheet reflects the current queue with nothing duplicated.
-
3
Slack - post the morning digest
slack.com
WebRun opens Slack to post the morning digest. - Post a short digest grouped by status with the count in each stage
- Call out the oldest three orders by days open
- Link to the full sheet for anyone who wants the detail
Done when Your team has this morning's pending-order snapshot in Slack.
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 this change anything in TazWorks?
No. It only reads order status. Nothing is edited, submitted, or sent from TazWorks itself.
How far back does it look?
It only looks at orders that are currently open, so a completed or canceled order drops off the digest on its own the next run.
Can I see more detail than the Slack summary?
Yes. Every pending order is also logged to a Google Sheet with its status, days open, and assigned researcher, so you can drill in beyond the digest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.