Your Team's Velocity, Calculated Automatically
How many issues did your team close this week? Notis logs each closure automatically, so velocity is always current and accurate.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Execute ClickHouse Query
Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.
Why this helps
Measuring velocity means manually counting closed issues each week. This is tedious, error-prone, and takes cognitive effort you'd rather spend on actual work.
- Every closed issue auto-logged for velocity calculation
- No manual counting, no human error in throughput metrics
- Historical velocity data for trend analysis and team performance insight
Setup
Build it in a few focused steps.
- 1Connect Linear and ClickHouse to Notis.
- 2Tell Notis: 'When an issue closes in Linear, log it to my velocity table with close date, team, and estimate if available.'
- 3Notis sets the Issue Updated trigger to fire when status changes to Done.
- 4Pick Slack, email, or Telegram for run reports.
- 5Test by closing an issue and verifying it appears in your velocity table.
Questions about this workflow
Does this account for issue size or complexity?
If you use estimate fields or size labels, tell Notis to include them. Otherwise it counts issues, but you can weight them in queries.
How often should I review velocity?
Daily data gives you trends. Weekly summaries give you sprint numbers. Notis calculates it constantly, so you can query any way you need.
Can I track velocity by team or individual?
Yes. Notis logs the assignee and team, so you can slice velocity data however you want for analysis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to ClickHouse. A trigger fires from one place; an action lands in another.
Linear triggers
ClickHouse actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute ClickHouse Query
Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Database Schema
Get comprehensive schema overview of an entire database including all tables and optionally their column definitions. essential for ai agents to understand the complete database structure in a single call.
Comment Received Trigger
Triggered when a comment is received.
Get Table Schema
Get detailed schema information for a specific table including column definitions, types, keys, and optionally sample data. this is essential for ai agents to understand table structure before constructing queries.
Issue Created Trigger
Triggered when a new issue is created.
List ClickHouse Databases
List all databases in the clickhouse instance. useful for discovering available databases before querying tables.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
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 ClickHouse, 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 ClickHouse.