All templates
For engineering managers, software teams & GitHub-based teams

Start your day with a ZenHub blocked issue digest

Every morning, WebRun opens ZenHub, checks issues marked blocked in the current sprint, books a short triage slot on Google Calendar if anything has been stuck more than 2 days, and posts the digest to your engineering Teams channel.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 ZenHub find blocked issues in the sprint
2 Google Calendar block a triage slot
3 Microsoft Teams post the blocked issue digest
Run a sample
In short

How do I get a daily digest of blocked ZenHub issues?

WebRun checks ZenHub every morning for issues marked blocked in the current sprint, books a short triage slot on Google Calendar if anything has been stuck more than 2 days, and posts the digest to your engineering Teams channel grouped by epic. Blocked work gets a scheduled path to resolution instead of just sitting flagged.

  • Blocked issues get a scheduled triage slot instead of just a flag
  • The engineering team starts the day with one grouped digest
  • Issues stuck under 2 days don't clutter the calendar

Built for engineering managers · software teams · GitHub-based teams · scrum masters

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.zenhub.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    ZenHub - find blocked issues in the sprint
    zenhub.com
    WebRun in ZenHub: find blocked issues in the sprint
    WebRun opens ZenHub to find blocked issues in the sprint.
    • Open ZenHub and check issues marked blocked in the current sprint pipeline
    • Note each issue's assignee, epic, and how long it's been blocked
    • Flag issues blocked more than 2 days

    Done when Every blocked issue in the current sprint is listed with its assignee.

  3. 2
    Google Calendar - block a triage slot
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: block a triage slot
    WebRun opens Google Calendar to block a triage slot.
    • Block a short triage slot today if any issue has been blocked more than 2 days
    • Title it with the number of blocked issues
    • Skip booking if nothing is blocked that long

    Done when A triage slot is booked when blocked issues need attention.

  4. 3
    Microsoft Teams - post the blocked issue digest
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: post the blocked issue digest
    WebRun opens Microsoft Teams to post the blocked issue digest.
    • Post the blocked issue digest to the engineering Teams channel
    • Group by epic
    • Note which issues are blocked more than 2 days

    Done when The team has today's blocked issue digest in Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.zenhub.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Blocked digest · Microsoft Teams
OutputWhat each run produces - A daily digest of blocked ZenHub issues, with a triage slot booked for anything stuck.
Digest
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it unblock or edit any issues?

No. WebRun only reads which issues are marked blocked in ZenHub. It never edits, unblocks, or reassigns an issue.

Why book a calendar slot only sometimes?

A triage slot is only worth booking when something has been stuck more than 2 days, so the calendar doesn't fill up with meetings for issues that clear themselves.

Does it read straight from GitHub issues?

It reads the blocked status and pipeline as tracked in ZenHub, which layers on top of your GitHub issues.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.