Never Wonder Which Baserow Database Owns Your New Work
When a new issue lands in Linear, your automation instantly shows you which Baserow workspace should own it. No more hunting through multiple databases.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
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.
Why this helps
New issues in Linear sit isolated because you never know which Baserow database should track them.
- Reduce context-switching between Linear and Baserow
- Never lose track of where work actually lives
- Eliminate duplicate effort on routing decisions
Setup
Build it in a few focused steps.
- 1Connect your Linear workspace and Baserow account to Notis through the portal (one-time setup).
- 2Go to Automations and create a new automation with trigger 'Issue Created'.
- 3Write this instruction: 'When a new Linear issue is created, list all Baserow databases and suggest which one should track this work based on the issue type and team.'
- 4Select your Notis channel to receive reports about each routed issue.
- 5Test by creating a sample issue in Linear and confirm the database suggestion appears.
Questions about this workflow
What happens if I have many Baserow databases?
Notis lists all of them so you can quickly identify the right one. Your automation instruction can specify how Notis should prioritize (e.g., 'prefer the database matching the team name').
Can this work with private Linear teams?
Yes. Use the 'Private Team Issue Created' trigger instead for issues in private teams.
Do I need to update my automation when I add new databases?
No. The automation lists your current databases each time it runs, so new ones are automatically discovered.
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.