Understand Your Issue Pipeline
Who creates most of your issues? Notis logs every new issue with creator so you see patterns, identify key reporters, and understand your issue pipeline.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
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
You don't know where your issues come from. Some team members create lots, others create none. You can't tell if your process is balanced or who should focus on writing better issues.
- Complete record of who creates issues for process analysis
- Identify key issue reporters and validation sources
- Understand your issue pipeline sources for process improvement
Setup
Build it in a few focused steps.
- 1Connect Linear and ClickHouse to Notis.
- 2Tell Notis: 'Every time a new Linear issue is created, log it with the creator name, timestamp, team, and issue type.'
- 3Notis sets the Issue Created trigger automatically.
- 4Choose Slack or email for notifications.
- 5Test by creating a new issue and checking that your name appears in the creator tracking table.
Questions about this workflow
Can I see how many issues each person creates?
Yes. Count issues grouped by creator to see who's most prolific at reporting.
Does this include issues created by bots or integrations?
Yes, it logs those too. You can filter them out if you only want human-created issues.
How do I use this data?
Identify issue quality leaders, spot bias in reporting, and improve your intake processes based on patterns.
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.