Give unowned compliance issues a clear next owner
A scheduled cross-check can carry an owner from 21risk to a linked GitHub issue that needs one.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A compliance action can have a responsible person while its related GitHub issue remains unassigned.
- Makes issue ownership clearer across compliance and engineering.
- Helps reduce follow-up caused by mismatched ownership.
- Lets teams review unassigned linked work on a predictable schedule.
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 21risk actions with an owner and assign that GitHub user to the linked issue when it is unassigned.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real action that includes an assignable owner and an existing GitHub issue reference.
Questions about this workflow
What data is required to connect an action to an issue?
The action must provide or be associated with a GitHub repository and issue reference, and the owner must have a GitHub username.
Can this workflow assign someone who lacks repository access?
GitHub assignment may be ignored if the authenticated user lacks push access or the person cannot be assigned to issues in that repository.
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.