Your Sprint Scope Stays Visible Across Systems
Update a sprint in Linear and Notis immediately checks your Baserow tracking tables to ensure capacity and commitment are in sync.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Action
List Tables in Database
This tool lists all tables within a specified baserow database. it allows users to retrieve information about all tables in a database by using the get /api/database/{database id}/tables/ endpoint. the expected output is an array of table objects containing details such as id, name, order, database id, type, and first row header.
Why this helps
Linear sprint scope and Baserow capacity records drift out of sync, creating confusion about what is actually committed.
- Keep sprint scope consistent across tools
- Prevent over-commitment surprises
- Reduce sprint planning confusion
Setup
Build it in a few focused steps.
- 1Connect Linear and Baserow to Notis.
- 2Create a new automation with trigger 'Project Properties Updated'.
- 3Write: 'When a project's sprint properties change, list Baserow tables and verify the capacity and scope are consistent in the sprint-tracking table.'
- 4Set your notification channel.
- 5Update a project's sprint scope in Linear and verify Notis checks your Baserow capacity records.
Questions about this workflow
What if Linear and Baserow have different capacity numbers?
Notis can alert you so you can reconcile them, or your prompt can specify which source is authoritative.
Can this work for multiple sprints?
Yes. Your automation can run for all projects and sync each sprint independently.
Can I include team member capacity in this sync?
Yes. Your automation prompt can include individual assignments as part of the capacity check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Baserow. A trigger fires from one place; an action lands in another.
Linear triggers
Baserow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Databases
This tool retrieves a list of all databases in a specified workspace. as a fundamental operation, it allows users to discover which databases are available in their baserow workspace. this operation is independent and requires only authentication in order to fetch essential metadata for subsequent operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Tables in Database
This tool lists all tables within a specified baserow database. it allows users to retrieve information about all tables in a database by using the get /api/database/{database id}/tables/ endpoint. the expected output is an array of table objects containing details such as id, name, order, database id, type, and first row header.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Baserow, 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 Baserow.