Turn stalled Beeminder goals into visible GitHub work
Keep a stalled goal from disappearing into another dashboard. Notis checks Beeminder and labels the related GitHub issue when progress needs attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
A goal can fall behind while its related GitHub issue sits unnoticed, creating another manual check and follow-up.
- Spot stalled work in the issue tracker you already use.
- Reduce manual checks across Beeminder and GitHub.
- Keep follow-up attached to the relevant issue.
Setup
Build it in a few focused steps.
- 1Connect Beeminder and GitHub once in the Notis portal.
- 2In Automations, choose New Automation and give it a name and prompt.
- 3Tell Notis to check Beeminder progress and label the related GitHub issue when a goal has stalled.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real Beeminder goal and its related GitHub issue.
Questions about this workflow
Does Beeminder provide the trigger for this automation?
No. Beeminder has no listed trigger events, so this workflow uses a Notis schedule to check goal progress.
How does Notis identify the related issue?
Describe how to find the matching issue in your instruction. If the relationship is not available in the connected data, provide the issue reference in the instruction or request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beeminder to GitHub. A trigger fires from one place; an action lands in another.
Beeminder triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Beeminder and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.