Keep changing plans close to current data
When a planning page changes, Notis can query ClickHouse for relevant signals to help you review the new direction.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
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
Plans evolve, but the metrics used to make the original decision can quickly become stale or hard to find.
- Revisit plan assumptions with current data.
- Avoid restarting analytics research from scratch.
- Make page edits easier to turn into considered decisions.
Setup
Build it in a few focused steps.
- 1Connect Notion and ClickHouse to Notis once.
- 2In the portal, create an automation, or ask Notis conversationally to build one.
- 3State one instruction asking for a ClickHouse query relevant to the changed planning page.
- 4Select Page Content Updated and choose a channel for run reports.
- 5Test by making one meaningful edit to a real plan page.
Questions about this workflow
Does it run for page body edits?
Yes. Page Content Updated is the trigger for body content updates, with Notion aggregating edits over a short window.
Can I limit this to one planning page?
Describe the page context in the prompt and select any available trigger scope when creating the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to ClickHouse. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
List ClickHouse Databases
List all databases in the clickhouse instance. useful for discovering available databases before querying tables.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.