Keep Bugherd ownership aligned with GitHub
Route a Bugherd report to the GitHub issue owner it names, without retyping the assignment.
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 reported owner can be easy to miss when ownership is recorded in Bugherd but the work happens in GitHub.
- Carry specified GitHub usernames into issue assignment.
- Reduce follow-up to align ownership across tools.
- Keep each assignment tied to a linked report.
Setup
Build it in a few focused steps.
- 1Connect Bugherd and GitHub once in Notis.
- 2Create an automation in Notis with a name and prompt.
- 3Describe how to add the report's specified GitHub usernames to its linked issue.
- 4Choose the Notis webhook trigger and where run reports should go.
- 5Test with a real report that includes a GitHub repository, issue number, and assignee usernames.
Questions about this workflow
Can this translate a Bugherd name into a GitHub username?
Only if the username is included or you provide a reliable mapping in the instruction. The workflow should not guess identities.
What happens if GitHub ignores an assignment?
GitHub may silently ignore assignment changes when the authenticated user lacks push access. Check the run report and repository permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugherd to GitHub. A trigger fires from one place; an action lands in another.
Bugherd 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.
Bugherd 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.