Skip to content
Notis

Look up ClickHouse table structure from an assigned issue

When an assigned issue asks how a specific ClickHouse table is structured, Notis can retrieve its schema so you can plan the query without opening another tool.

Trigger

New Issue Assigned to Me

Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.

Action

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.

Why this helps

Query work stalls when the relevant column names and types are hidden behind a separate schema lookup.

  • See the named table’s columns and types in the context of the assigned work.
  • Avoid returning sample data when the task only needs structural details.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and ClickHouse to Notis once in the portal.
  • 2Create the automation in the portal or ask Notis for it in plain language.
  • 3Tell Notis to retrieve schema only when an assigned issue explicitly names a ClickHouse database and table, and not to include sample rows.
  • 4Select GitHub New Issue Assigned to Me and choose where run reports should go.
  • 5Test with one assigned issue that names an existing database and table.

Questions about this workflow

Does it run a query against the table?

No. This workflow retrieves the table schema, including column definitions and types, and does not execute SQL.

Does it return sample rows?

No. The instruction requests structural details only and excludes optional sample data.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to ClickHouse. A trigger fires from one place; an action lands in another.

GitHub triggers

ClickHouse actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Execute ClickHouse Query

Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

TriggerPolling

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.

ActionInstant

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

List ClickHouse Databases

List all databases in the clickhouse instance. useful for discovering available databases before querying tables.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

List ClickHouse Tables

List tables in clickhouse databases. returns information about tables including their engine, size, and row count.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub 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.