Triage Borneo findings into GitHub on a schedule
Set a recurring review so Borneo findings with a matching GitHub issue receive a useful label without waiting for someone to triage them manually.
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
Findings can accumulate between reviews, leaving remediation issues hard to distinguish from routine work.
- Create a predictable review rhythm for available findings.
- Make related remediation issues easier to scan.
- Reduce the need to remember a separate manual triage pass.
Setup
Build it in a few focused steps.
- 1Connect Borneo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to review available Borneo findings and add an appropriate label to each corresponding GitHub issue identified by repository and issue number.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real finding that maps to an existing GitHub issue.
Questions about this workflow
Does the schedule discover findings automatically?
The schedule starts the automation. Your instruction must tell Notis to review the findings available through the connected Borneo app.
What happens if there is no matching issue?
The GitHub label action requires an existing issue. Supply a repository and issue number, or instruct Notis to report unmatched findings for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Borneo to GitHub. A trigger fires from one place; an action lands in another.
Borneo 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.
Borneo 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.