Prepare Kaggle dataset metadata from Linear
Turn dataset publishing preparation into a tracked step, with Notis initializing the metadata file and reporting back.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Kaggle Dataset Init
Tool to initialize a dataset-metadata.json file in a local folder. Use when preparing a dataset folder before uploading to Kaggle.
Why this helps
Publishing prep involves small steps that are easy to forget when attention is split across tasks.
- Adds a repeatable preparation step to the issue workflow.
- Reduces missed metadata setup when packaging a dataset.
- Keeps the result close to the task asking for it.
Setup
Build it in a few focused steps.
- 1Connect Linear and Kaggle to Notis once in the portal.
- 2Create an automation or tell Notis to initialize Kaggle dataset metadata when a Linear preparation issue is created.
- 3Use one plain-language instruction that identifies the local folder and asks for a result report.
- 4Select the Linear Issue Created trigger and choose a channel for run reports.
- 5Test with an issue that names a prepared dataset folder.
Questions about this workflow
Does this upload the dataset?
No. It initializes a metadata file in a local folder for preparation.
What does the issue need to identify?
Include the folder to prepare so Notis can initialize metadata in the intended location.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Kaggle. A trigger fires from one place; an action lands in another.
Linear 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).
Comment Received Trigger
Triggered when a comment is received.
Dataset Create
Tool to create a new Kaggle dataset with full metadata. Use after uploading files and finalizing metadata. Returns creation status and message.
Issue Created Trigger
Triggered when a new issue is created.
Get Dataset Status
Tool to get the status of a dataset upload or processing job. Use after uploading a dataset to check processing state.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.