Surface overdue compliance work in GitHub
Let a scheduled check bring overdue 21risk tasks back into view on their related GitHub issues.
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
Overdue compliance work can be easy to miss when its status lives outside the engineering queue.
- Surfaces overdue work where engineering reviews issues.
- Cuts down on manual cross-checking between 21risk and GitHub.
- Uses a consistent label to help teams triage delayed work.
Setup
Build it in a few focused steps.
- 1Connect 21risk and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to review overdue 21risk tasks and add an overdue label to each linked GitHub issue, using the repository and issue references available for those tasks.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with one real overdue task that has a linked GitHub issue.
Questions about this workflow
How does the workflow know a task is overdue?
Notis can use the due date and status available from 21risk. If those are not available, supply the needed details in the prompt or task data.
Does this workflow create missing GitHub issues?
No. It labels linked issues, so each task needs an existing GitHub issue reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to GitHub. A trigger fires from one place; an action lands in another.
21risk 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.
21risk 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.