FetchGithubIssues
Checks a GitHub repository for a tracked issue every morning and pushes its current status to WhatsApp so nothing sits unnoticed.
Use this templateWhy use it
There is one issue in the repo that everything else is waiting on — a blocking bug, a customer escalation, the ticket the release depends on. Nobody remembers to open GitHub and look at it, so it sits in the same state for four days while people assume someone else is on it. You only find out it never moved when the deadline arrives, or when the customer asks again.
How it works
- 1Every morning, the check kicks off on its own at the time you pick — you never have to remember to go look.
- 2GitHub is searched for the issue you're tracking in the repository you named, and its current record is pulled back: the title, whether it's still open or closed, and the details attached to it.
- 3That status arrives as a WhatsApp message on your phone, so the state of the issue is sitting in your chat list before you start work instead of buried in a browser tab you didn't open.
What it connects
- Schedule
- GitHub
- WhatsScale
Questions
How do I tell it which issue to watch?
You configure the repository owner, the repository name, and the issue you want looked up when you set up the GitHub step. It checks that same one on every run, so this is best for a specific ticket you care about rather than a whole backlog.
Can I change what time the morning message arrives?
Yes. The schedule is a single setting on the trigger step — pick the hour that suits your standup or the start of your day, and every run after that follows it.
Does it only message me when something changes?
No. It reports the current status every single morning, whether or not anything moved. That is deliberate: an unchanged status four days in a row is exactly the signal that tells you the issue is stuck.
Will this work with a private repository?
Yes, as long as the GitHub connection you authorise has access to that repository. Private repos behave the same way as public ones once the credential can read them.
Can the message go to a team group instead of just me?
Yes. The WhatsApp step sends to whichever number or group chat you set as the recipient, so a shared engineering group works just as well as your personal chat.
What happens if the issue can't be found?
If the lookup fails — wrong repository name, a deleted issue, or a revoked credential — the run stops at that step and no message goes out. A silent morning is worth checking your configuration over.