Connect 0CodeKit to Bench

When something happens in 0CodeKit, Notis takes the next step in Bench. 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 0CodeKit to Bench

View example

Pause Before a Benchmark Rate Limit Window

Hold a Bench workflow briefly after a 0CodeKit request so bursty benchmark traffic can settle.

View example

Add a Nightly Benchmark Settling Window

Insert a short nightly pause before scheduled Bench work so queued 0CodeKit jobs can finish settling.

View example

Wait Between Retry Attempts

Use a 0CodeKit webhook to pause between retry attempts when a Bench run needs backoff time.

View example

Create an Hourly Benchmark Cooldown

Run a recurring cooldown pause to keep scheduled Bench activity from bunching together.

View example

Pause After Document Conversion

Wait after a 0CodeKit document conversion webhook so downstream benchmark preparation has time to settle.

View example

Buffer a Weekly Report Generation Window

Add a scheduled pause before a weekly benchmark reporting routine that depends on 0CodeKit generation work.

View example

Add an Image Processing Cooldown

Pause after a 0CodeKit image processing request to space out the next Bench operation.

View example

Wait Before a Monthly Baseline Refresh

Schedule a monthly Bench pause before a baseline refresh routine that follows 0CodeKit data preparation.

View example

Hold for a Validation Review Buffer

Pause after a 0CodeKit validation webhook to leave room for a human review before Bench work continues.

Supported Triggers and Actions

Notis builds workflows that link 0CodeKit to Bench. A trigger fires from one place; an action lands in another.

0CodeKit triggers

Bench actions

Recurring trigger

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

TriggerScheduled

Sleep

ActionInstant

Webhook trigger

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

TriggerInstant

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.