Connect Abuselpdb to ClickHouse

When something happens in Abuselpdb, 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 Abuselpdb to ClickHouse

View example

Log Abuselpdb Abuse Reports in ClickHouse

Send report data from an Abuselpdb workflow to a webhook and insert the supplied records into a ClickHouse table.

View example

Save IP Reputation Checks to ClickHouse

Capture IP reputation results supplied to a webhook and append the provided snapshot to ClickHouse.

View example

Create a ClickHouse Queue for Reported IPs

Insert supplied abusive IP reports into a ClickHouse review table with the context included in each webhook payload.

View example

Record Threat Intelligence Events in ClickHouse

Store threat intelligence events supplied by an external Abuselpdb caller in a ClickHouse table for later analysis.

View example

Summarize New Abuse Reports in ClickHouse

On each webhook request, query supplied or previously stored report data in ClickHouse and return a concise summary in the run report.

View example

Review Stored IP Reputation Data on a Schedule

Run a scheduled ClickHouse query over previously stored IP reputation results and summarize the returned data in the run report.

View example

Review the ClickHouse Schema for Abuse Data

On a schedule, retrieve the ClickHouse database schema and summarize the tables and columns relevant to your stored abuse data.

View example

Inventory ClickHouse Threat Data Tables

On a schedule, list ClickHouse tables and review their names, engines, sizes, and row counts when those details are returned.

View example

Check ClickHouse Databases for Threat Analytics

List databases on a schedule and summarize the available ClickHouse locations for threat data analysis.

Supported Triggers and Actions

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

Abuselpdb triggers

ClickHouse actions

Recurring trigger

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

TriggerScheduled

Execute ClickHouse Query

Runs a database query and returns the results.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Database Schema

Retrieves an overview of a database's schema and tables.

ActionInstant

Get Table Schema

Gets the schema and column details for a table.

ActionInstant

Get ClickHouse Play Interface

Returns the ClickHouse Play interface for writing queries and viewing results.

ActionInstant

List ClickHouse Databases

Lists the databases in an instance.

ActionInstant

List ClickHouse Tables

Lists tables in databases with basic details.

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.