Check issue assignment eligibility before routing work
Confirm the intended owner is assignable on the issue before you rely on them to move image enhancement work forward.
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 to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
An assignment plan can fail when the intended owner is not eligible for that repository issue.
- Verifies a user can be assigned to a specified issue
- Helps prevent invalid assignment expectations
- Makes ownership reviews easier to run routinely
Setup
Build it in a few focused steps.
- 1Connect Claid AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to check whether the specified GitHub user can be assigned to the named issue and summarize the result.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real issue and user and confirm GitHub's response is reflected in the report.
Questions about this workflow
Does this action assign the user?
No. It checks whether the user can be assigned to the specified issue.
What information is needed?
Identify the repository, issue, and GitHub user in the instruction or the context supplied to Notis.
Can a failed check fix access?
No. The action reports assignability; any access or repository changes require a separate decision.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Claid ai to GitHub. A trigger fires from one place; an action lands in another.
Claid ai 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.
Claid ai 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.