Turn a Beeminder review request into assigned GitHub follow-up
When a goal needs someone to act, start a review request and have Notis assign the related GitHub issue using the owner you specify.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Reviewing progress and then separately finding and assigning the issue adds friction to follow-through.
- Make issue ownership part of the goal review.
- Start follow-up when a review request arrives.
- Keep action tied to the corresponding GitHub 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 review the requested goal and assign the related GitHub issue to the owner you specify when follow-up is needed.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test by starting the webhook with a real goal, issue, and intended assignee.
Questions about this workflow
Can the workflow choose an assignee automatically?
Only if your instruction specifies the owner or the needed ownership information is available in the data Notis can access.
What does the webhook trigger do?
A Notis webhook starts when an HTTP request reaches it. Beeminder has no listed trigger events, so this is an on-demand request rather than an automatic Beeminder event.
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.