Validate issue ownership for incoming chain alerts
Before routing an alert to a specific issue owner, check that GitHub will accept the assignment.
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
A well-intended handoff can still stall if the proposed owner cannot be assigned to the particular issue.
- Check eligibility in the context of the exact issue.
- Reduce failed assignment attempts during incident routing.
- Keep ownership validation attached to the incoming alert.
Setup
Build it in a few focused steps.
- 1Connect Alchemy and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to check the proposed username against the repository and issue identified in the alert.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real alert and confirm the specific issue assignment check result.
Questions about this workflow
How is this different from checking repository assignability?
This action checks whether a user can be assigned to a given issue in a repository, while the general check does not specify an issue.
Does it assign the user if they are eligible?
No. It only checks eligibility. Use an assignment action separately if you want to update the issue.
What should the webhook include?
Include or make available the repository, issue number, and proposed username so Notis can perform the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Alchemy to GitHub. A trigger fires from one place; an action lands in another.
Alchemy 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.
Alchemy 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.