Make every deployment easier to follow
Notis checks the experiment side of a new deployment so you do not have to remember another operational step.
Trigger
New Deployment Created
Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.
Action
Get Kernel Status
Tool to get the status of a Kaggle kernel run. Use after submitting a kernel to monitor its execution state.
Why this helps
New deployments create a burst of tasks, making experiment verification easy to skip.
- Reduce post-deployment task load
- Keep experiments visible during releases
- Get a clear status without dashboard hopping
Setup
Build it in a few focused steps.
- 1Connect GitHub and Kaggle to Notis once through the portal.
- 2Create an automation and tell Notis: When a new GitHub deployment is created, check the related Kaggle kernel status and report whether the deployment handoff is complete.
- 3Select the new deployment created trigger and choose the channel for run reports.
- 4Test it in a staging environment.
Questions about this workflow
Can it monitor staging first?
Yes. Configure the GitHub trigger for the staging deployment before expanding it to production.
What does complete mean?
Define it in the instruction, such as a successful deployment plus a completed Kaggle kernel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Kaggle. A trigger fires from one place; an action lands in another.
GitHub triggers
Kaggle actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Download competition data files
Tool to download competition data files. Use after confirming the competition ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Initialize Kaggle Configuration
Tool to initialize Kaggle API client configuration. Attempts CLI first; if unavailable, it falls back to creating ~/.kaggle/kaggle.json (or $KAGGLE_CONFIG_DIR/kaggle.json).
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Dataset Create
Tool to create a new Kaggle dataset with full metadata. Use after uploading files and finalizing metadata. Returns creation status and message.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get Dataset Status
Tool to get the status of a dataset upload or processing job. Use after uploading a dataset to check processing state.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Dataset Version
Tool to create a new dataset version on Kaggle. Use when you have updated files or metadata and need to publish a new version of an existing dataset.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Submit Competition Entry
Tool to submit an entry to a Kaggle competition. Use when you have already uploaded your file and obtained its blob token.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Kaggle Config Directory
Tool to retrieve the directory of the Kaggle API configuration file. Use when you need to locate the directory containing your kaggle.json credentials.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Kaggle Config File
Tool to retrieve the filename of the Kaggle API configuration file. Use when you need to find out where the local Kaggle config file is stored before reading or updating.
Connect any two apps with Notis in the middle.
GitHub and Kaggle, 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 Kaggle.