Route client requests to the right GitHub issue owner
Send a Bonsai client request to Notis and update the assignees on its related GitHub issue.
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
Client requests arrive through Bonsai, while the GitHub issue that needs attention remains unassigned or with the wrong owner.
- Make issue ownership visible alongside the work
- Cut down on follow-up to assign incoming requests
- Use the assignee specified in the request or agreed team rules
Setup
Build it in a few focused steps.
- 1Connect Bonsai and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, tell Notis to use the incoming Bonsai request to identify its GitHub issue and add the specified assignee.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real request and verify the issue and assignee.
Questions about this workflow
Can this assign any GitHub user?
The target user must be assignable in the repository. Include their GitHub username or a clear rule for identifying them in the request.
Does the webhook choose the repository automatically?
Notis needs enough information in the request or its instructions to identify the repository and issue.
What if I do not include an assignee?
Tell Notis in the prompt how to handle missing ownership details, such as leaving the issue unchanged and reporting that information is needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bonsai to GitHub. A trigger fires from one place; an action lands in another.
Bonsai 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.
Bonsai 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.