Keep Jira reporting data sources visible
Get a recurring snapshot of ClickHouse tables so reporting owners can spot what sources are available before they need them.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
Why this helps
Useful analytics tables become hard to find when reporting knowledge lives in scattered notes and team memory.
- Make available ClickHouse tables easier to discover.
- Reduce repeated searching when new Jira reporting questions come up.
- Create a regular prompt to review table engines, sizes, and row counts when returned.
Setup
Build it in a few focused steps.
- 1Connect ClickHouse once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to list ClickHouse tables on a recurring schedule and summarize the returned inventory for Jira reporting.
- 4Pick a schedule trigger and choose where run reports should go.
- 5Test with one real run and review the table inventory.
Questions about this workflow
Does the inventory explain every table's columns?
No. The table list includes table information such as engine, size, and row count. Use a schema action when you need column details.
Can I use this to verify which tables contain Jira data?
The inventory alone does not establish that. Ask Notis to summarize names and details returned, then confirm the data source with your team or schema inspection.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to ClickHouse. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
List ClickHouse Databases
List all databases in the clickhouse instance. useful for discovering available databases before querying tables.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
Connect any two apps with Notis in the middle.
Jira 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.