Connect Box to ClickHouse
When something happens in Box, Notis takes the next step in ClickHouse. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Box to ClickHouse
Check ClickHouse data after a Box file version changes
Query ClickHouse when a Box file gets a new version, so you can spot changes in the data that depends on it.
Inspect ClickHouse table structure for new Box files
When a new file lands in a Box folder, retrieve a selected ClickHouse table's schema to support your review.
Run a ClickHouse follow-up when a Box file gets a comment
Use a new Box file comment to trigger a ClickHouse query that checks the analytics behind a question or request.
Review ClickHouse database structure for a new Box collaborator
When a new collaboration is created on a Box folder, retrieve a ClickHouse database overview for an instructed access or project review.
List ClickHouse databases after Box file metadata changes
When a monitored Box file's metadata changes, list available ClickHouse databases to support a source or analytics review.
Refresh a ClickHouse schema reference after a Box comment changes
When a monitored Box comment changes, retrieve a specified ClickHouse table schema to keep the data context close to the discussion.
Review ClickHouse tables when a new Box folder item arrives
When a new item appears in a Box folder, list ClickHouse tables in a specified database to help orient a data review.
Run a ClickHouse access review when a Box file link changes
When a Box file's shared link settings change, run a specified ClickHouse query to support your access or activity review.
Check ClickHouse data when a Box task assignment changes state
When a Box task assignment is completed, approved, or rejected, run a relevant ClickHouse query and report the results.
Supported Triggers and Actions
Notis builds workflows that link Box to ClickHouse. A trigger fires from one place; an action lands in another.
Box 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.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
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 Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
List ClickHouse Databases
List all databases in the clickhouse instance. useful for discovering available databases before querying tables.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Box and ClickHouse
Connect any two apps with Notis in the middle.
Box 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.