Give model latency follow-up a clear owner
When provider or model speed changes, direct the related GitHub work to the people who can investigate it.
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
Latency shifts can create investigation work, but the signal and its GitHub follow-up often get separated.
- Create clear ownership for latency-related investigation.
- Keep provider and model performance reviews connected to work.
- Reduce the chance that speed regressions go unexamined.
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 which latency or throughput changes matter, how to find related issues, and who should follow up.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real performance change and a relevant issue.
Questions about this workflow
Does this detect a regression against our own baseline?
Artificial Analysis data does not necessarily include your product's baseline. Supply your comparison threshold or baseline in the instruction if the review depends on it.
Can it assign someone outside the repository?
GitHub assignment is subject to repository access and assignability. Use an eligible account and check the run report for issues that could not be assigned.
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.