Connect Agent mail to ClickHouse

When something happens in Agent mail, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Agent mail to ClickHouse

View example

Log New AgentMail Emails in ClickHouse

Record each newly received AgentMail email in a ClickHouse table for searchable reporting and analysis.

View example

Summarize Daily AgentMail Inbox Volume

Run a daily ClickHouse query to summarize AgentMail message volume from email records already stored in your database.

View example

Check ClickHouse Schema for Incoming Email Records

When an AgentMail message arrives, retrieve a ClickHouse table schema to help inspect a candidate destination before writing email data.

View example

Create an On-Demand ClickHouse Email Data Map

Start from an HTTP request and retrieve an overview of a ClickHouse database to understand tables available for email analytics.

View example

Review ClickHouse Databases for Email Analytics

On a schedule, list available ClickHouse databases to keep track of where email analytics data could live.

View example

Find ClickHouse Tables for an Email Report

Use a webhook to list tables in a specified ClickHouse database before building an email report.

View example

Review AgentMail Response Times from Stored Data

Query existing ClickHouse email records on a schedule to summarize response times when the data includes the needed timestamps and thread links.

View example

Analyze New AgentMail Email Against Existing Trends

When a new message arrives, query relevant ClickHouse history to compare it with trends in records you already store.

Supported Triggers and Actions

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

Agent mail 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 Email Received

Trigger for new emails in an AgentMail inbox

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

List ClickHouse Databases

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

ActionInstant

List ClickHouse Tables

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

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.