Route Blackboard walkthrough blockers to GitHub owners
A blocked walkthrough should create momentum, not another tab to remember.
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
Technical blockers discovered during Blackboard walkthroughs often remain in messages instead of entering the development queue.
- Turns blockers into actionable engineering work
- Preserves context from the original report
- Shortens the path from discovery to ownership
Setup
Build it in a few focused steps.
- 1Connect Blackboard and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create and assign a GitHub issue for each Blackboard walkthrough blocker, preserving the relevant context.
- 3Pick an incoming webhook trigger and choose the run-report channel.
- 4Test with one real blocker report.
Questions about this workflow
Can Notis distinguish blockers from general comments?
Yes. Define the words, severity, or conditions that should qualify as a blocker in the instruction.
Will the original context be retained?
Notis can include the relevant Blackboard details in the GitHub issue content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blackboard to GitHub. A trigger fires from one place; an action lands in another.
Blackboard triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Blackboard and GitHub. Any 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.