Skip to content
Notis

See How Campaign Delivery Tracks Against Plan

Get a recurring pacing summary that compares available delivery data with the targets your team supplies.

Trigger

Recurring schedule

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

Action

Execute ClickHouse Query

Runs a database query and returns the results.

Why this helps

Pacing checks can fall behind when delivery data and campaign plans live in separate places or are reviewed inconsistently.

  • Review delivery against a supplied plan or target.
  • Spot pacing gaps in a recurring report.
  • Make missing target inputs visible instead of assuming them.

Setup

Build it in a few focused steps.

  • 1Connect Adyntel and ClickHouse once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis the outcome in plain language from any channel.
  • 3Ask Notis to query campaign delivery and compare it with targets or a plan you provide, noting any missing inputs.
  • 4Pick a recurring schedule as the trigger and choose where run reports should go.
  • 5Test with one real example and confirm the target period and delivery values are comparable.

Questions about this workflow

Where does the plan or target come from?

Provide it in the prompt or make it available to the automation as context. ClickHouse results alone cannot supply a target that is not stored there.

Can it explain why a campaign is behind?

It can summarize queried data that may help explain pacing, but it cannot infer causes absent from the available records.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Adyntel 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

Connect any two apps with Notis in the middle.

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