Check issue assignment eligibility before you need it
Verify assignability for a named user and repository ahead of time, then keep the result available in your run reports.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user can be assigned
Verifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the response.
Why this helps
Finding out someone cannot be assigned during triage slows down issue handoffs and adds avoidable back-and-forth.
- Check a user's assignability for a repository
- Catch handoff friction before an issue needs assignment
- Keep a recurring record in run reports
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 eligibility check.
- 3Specify the GitHub username and repository to check.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real user and repository and review the result.
Questions about this workflow
Does this check whether a user can be assigned to a particular issue?
This action checks if a GitHub user can be assigned to issues in a repository generally. Use the separate issue-specific check when you need to check one issue.
Does the check assign the user?
No. It verifies eligibility only.
Can Browseai start the check?
No Browseai event triggers are listed. This workflow uses a Notis schedule.
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.