Check whether a person can be assigned to the issue in your signal
Use the signal context to check the exact issue and person, then receive an answer without changing the issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user can be assigned to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
When a signal points to a concrete issue, a general access check may leave the assignment question unanswered.
- Start from a Notis webhook request
- Check one user against one specific issue
- Receive a report without changing assignment
Setup
Build it in a few focused steps.
- 1Connect Browseai and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, then name it and describe the issue-specific check.
- 3Tell Notis to read the repository, issue number, and username from the incoming request context.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real signal and confirm the exact issue and user are checked.
Questions about this workflow
What starts this workflow?
A Notis webhook HTTP request starts it. Browseai has no trigger events in the supplied list.
Does it check a specific issue or the whole repository?
It checks whether the specified user can be assigned to the specified issue.
Will it update the issue?
No. The action only checks assignability.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browseai to GitHub. A trigger fires from one place; an action lands in another.
Browseai 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.
Browseai 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.