Route provider throughput follow-up to an owner
Make provider performance reviews easier to act on by giving related GitHub issues a clear owner.
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
Throughput changes can affect provider choices, yet related GitHub work can remain unassigned after a review.
- Assign follow-up for throughput changes that matter.
- Keep provider performance checks connected to engineering work.
- Reduce manual handoffs from review to issue ownership.
Setup
Build it in a few focused steps.
- 1Connect Artificial Analysis and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3Tell Notis what provider throughput changes matter, how to find related issues, and who should own them.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real throughput change and a relevant issue.
Questions about this workflow
Can it determine how much throughput we need?
Include your expected workload or throughput threshold in the instruction. Artificial Analysis data does not supply your product's capacity requirement.
Can it assign the same person to each issue?
Yes, if you name an eligible GitHub user in the instruction and that user can be assigned in the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Artificial Analysis to GitHub. A trigger fires from one place; an action lands in another.
Artificial Analysis 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.
Artificial Analysis 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.