Make a Beeminder check-in visible in GitHub
Request a review when you check in on a goal. Notis can look up the Beeminder progress and add a label to the related GitHub issue when your instruction's condition is met.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 manual goal review can end without the related issue reflecting what needs attention next.
- Review a goal when you choose to start the webhook.
- Carry a progress decision into the issue tracker.
- Keep the goal and its follow-up connected.
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 the requested Beeminder goal and label its related GitHub issue when your stated condition is met.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test by starting the webhook with one real goal and its related issue.
Questions about this workflow
Does the webhook start automatically when Beeminder changes?
No Beeminder trigger event is listed. The Notis webhook starts when an HTTP request reaches it; this setup does not assume a Beeminder event trigger.
What should the request identify?
Include enough context in the request or instruction to identify the Beeminder goal and the corresponding GitHub issue.
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.