Make model drift easier to triage
Turn monitoring output into a GitHub queue your team can read at a glance.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Model monitoring creates technical findings, but each one still needs manual interpretation and sorting.
- Creates a shared language for drift incidents
- Speeds up prioritization of model work
- Makes recurring patterns easier to notice
Setup
Build it in a few focused steps.
- 1Connect Databricks and GitHub to Notis once through the portal.
- 2Ask Notis to review scheduled model drift results and label matching GitHub issues with the model, drift category, and urgency.
- 3Select a daily cron trigger and the channel for run summaries.
- 4Test with one recent drift result and inspect the resulting labels.
Questions about this workflow
Can labels be created if they do not exist?
GitHub's label action can create labels that are not already present.
Can this cover multiple models?
Yes. Include the model names and the labeling convention in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Databricks to GitHub. A trigger fires from one place; an action lands in another.
Databricks triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Databricks and GitHub. Any 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.