Turn bug reports into owned GitHub issues
When an error report points to a known issue and owner, let Notis make the follow-up visible in GitHub.
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
A known error can remain unowned when its report and issue live in separate places.
- Put a clear owner on an existing issue when the report supplies one.
- Keep assignment grounded in information present in the report.
- Make follow-up easier to spot in GitHub.
Setup
Build it in a few focused steps.
- 1Connect Bug Recorder and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for issue ownership.
- 3Describe how to assign the related issue only when the report identifies a repository, issue, and assignable user.
- 4Choose the Notis webhook trigger and select a channel for run reports.
- 5Test with one real report that includes a valid issue and intended assignee.
Questions about this workflow
Does this choose an owner automatically?
Not by default. In your instruction, use an owner only when the report or your stated rules identify one. The selected GitHub action adds assignees to an existing issue.
What if the user cannot be assigned?
GitHub may reject or ignore an assignment when the user is not assignable or the authenticated user lacks the required repository access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bug Recorder to GitHub. A trigger fires from one place; an action lands in another.
Bug Recorder 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.
Bug Recorder 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.