Check issue assignment eligibility
Know who can take ownership before a handoff turns into another blocked task.
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
Issue assignment fails at the moment of handoff when contributor eligibility has changed since the last review.
- Reduce failed handoffs
- Keep assignment decisions current
- Make delegation easier to trust
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates and GitHub to Notis once through the portal.
- 2Create a recurring automation or ask Notis to create it conversationally.
- 3Use this instruction: On the chosen schedule, check whether the specified credentialed contributors can be assigned to issues in the named GitHub repository and report any exceptions.
- 4Select the recurring trigger, choose the run-report channel, and test with one contributor.
Questions about this workflow
Does this assign an issue?
No. It verifies assignability so you can route work with more confidence.
What does GitHub consider assignable?
GitHub determines eligibility for assignment based on the repository and user relationship.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Accredible certificates to GitHub. A trigger fires from one place; an action lands in another.
Accredible certificates 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.
Accredible certificates 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.