Roll up every mail job's status into one morning digest
Every morning, WebRun opens BCC Software, pulls every active job with its current production stage, logs the day's breakdown to a running Google Sheet, and posts your team a Slack digest summarizing counts per stage with any job at risk of missing its mail date called out first.
- No credit card
- Under $0.01 per run
- Cancel anytime
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.bccsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
BCC Software - pull every active job's stage
bccsoftware.com How to Automate BCC Software
WebRun opens BCC Software to pull every active job's stage. - Open BCC Software and pull every active job with its client, stage, and mail date
- Count jobs in each production stage: prepress, data processing, presort, print, insert, mail
- Flag any job whose mail date is within 2 days but not yet at the mail stage
Done when Every active job has a counted stage and a flag if its mail date is at risk.
-
2
Google Sheets - log the day's pipeline breakdown
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log the day's pipeline breakdown. - Open the shared pipeline tracker and add today's row of stage counts
- Log each at-risk job by name so the trend is visible over time
Done when Today's pipeline breakdown is logged alongside the last 30 days.
-
3
Slack - post the morning digest
slack.com How to Automate Slack
WebRun opens Slack to post the morning digest. - Post your team a digest of today's job counts by stage
- List any at-risk job first, naming the client and mail date
- Link back to the full breakdown in Google Sheets
Done when Your team has this morning's pipeline digest in Slack.
How do I get a daily summary of every mail job's production status?
Every morning, WebRun opens BCC Software and pulls every active job with its client, stage, and mail date. It counts jobs across each production stage, logs the breakdown to a running Google Sheet, and posts your team a Slack digest with any job at risk of missing its mail date flagged first.
- Every job's stage is visible in one digest each morning, not scattered across BCC Software
- At-risk jobs are called out first, before a mail date is missed
- 30 days of pipeline history builds automatically in Google Sheets
Built for lettershops · mailing houses · direct mail production managers · print and mail service bureaus
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 just count jobs, or does it flag problems too?
Both. It counts every active job by production stage, and separately flags any job whose mail date is within 2 days but has not yet reached the mail stage, so those show first.
Where can I see the trend over time, not just today?
In the Google Sheet. WebRun adds a new row of stage counts each morning, so you can scroll back and see how the pipeline has moved over the past 30 days.
Does the digest go to clients?
No. It posts only to your internal Slack channel. WebRun never shares job pipeline detail with a client on its own.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.