One Issue, Two Systems, Perfectly Synced
Issues that need to live in both Linear and Baserow are effortlessly synchronized. Just label them 'track-in-baserow' and Notis handles the rest.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_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
Some issues need to exist in both Linear (for development) and Baserow (for tracking), but manual duplication creates errors and dropped updates.
- Reduce manual duplication effort
- Keep parallel records in sync
- Never duplicate effort on key issues
Setup
Build it in a few focused steps.
- 1Connect Linear and Baserow to Notis.
- 2Create a new automation with trigger 'Public Team Issue Created'.
- 3Add this prompt: 'When a public issue is labeled track-in-baserow, list all Baserow databases and replicate this issue in the designated workspace.'
- 4Set your notification channel.
- 5Create a test issue, add the label, and verify it appears in Baserow.
Questions about this workflow
Which label should I use?
You can customize the label in your automation prompt. Use whatever naming makes sense to your team.
Can updates to the Linear issue sync back to Baserow?
Yes. Create a companion automation with trigger 'Issue Updated' using the same logic.
What if I want different databases for different issue types?
Notis can use multiple labels (e.g., track-in-baserow-dev, track-in-baserow-marketing) to route to different databases.
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.