Give unassigned GitHub issues a clear next owner
Have Notis review a supplied batch of issues on a schedule and assign the right people based on your instructions.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Issues without an owner can sit unnoticed while everyone assumes someone else will follow up.
- Create a regular ownership review without opening every issue yourself.
- Make assignment decisions using context you provide.
- Keep ownership visible in the issue tracker.
Setup
Build it in a few focused steps.
- 1Connect Apipie AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation.
- 3Describe how to review the issue context you provide and assign the appropriate GitHub users.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real issue example.
Questions about this workflow
Does the schedule automatically search all repository issues?
The listed action adds or removes assignees for a specified issue. Supply the issues and context to review, or use another grounded way to provide them.
What if an assignee cannot be added?
GitHub may silently ignore assignment changes when the authenticated user lacks push access to the repository.
Can AI decide who should own an issue?
Notis can use the context and assignment rules you describe, but provide the eligible GitHub usernames and any ownership criteria it needs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apipie ai to GitHub. A trigger fires from one place; an action lands in another.
Apipie 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.
Apipie 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.