Completed Work Gets Marked Done Everywhere
Move an issue to Done in Linear, and Notis checks your Baserow tables to ensure the record status is updated too, preventing stale closed items.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
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
Issues get closed in Linear but corresponding Baserow records stay open, creating confusion about what is actually complete.
- Prevent stale closed items in Baserow
- Keep completion status consistent across systems
- Reduce manual record cleanup
Setup
Build it in a few focused steps.
- 1Connect Linear and Baserow to Notis.
- 2Create a new automation with trigger 'Public Team Issue Properties Updated'.
- 3Write: 'When an issue is moved to Done, list Baserow tables and check if a matching record exists. If it does, verify the status is marked complete.'
- 4Choose your notification channel.
- 5Move a test issue to Done and confirm Notis checks the corresponding Baserow record.
Questions about this workflow
What if a Baserow record doesn't exist for a closed Linear issue?
Notis can alert you so you know if there's a tracking gap, or create the record retroactively.
Can this work for other status changes besides Done?
Yes. Modify your automation prompt to check any status (In Progress, Blocked, etc.).
What if I use different 'done' statuses in different databases?
Notis can be configured per database with custom status mappings in your prompt.
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.