Connect 0CodeKit to Bonsai

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

View example

Inspect a Bonsai cluster after a 0CodeKit request

Review one Bonsai cluster's configuration and status whenever a 0CodeKit workflow sends an inspection request.

View example

List Bonsai spaces for a provisioning request

Return available Bonsai spaces when a 0CodeKit workflow asks where a new cluster could run.

View example

Verify a Bonsai space before deployment

Retrieve metadata for a specific Bonsai space before a 0CodeKit deployment workflow proceeds.

View example

Refresh the Bonsai space inventory on demand

Fetch the complete list of Bonsai spaces when a 0CodeKit workflow needs a current account inventory.

View example

Review a Bonsai cluster status every morning

Run a daily review of a specified Bonsai cluster so its configuration and status are ready for the day.

View example

Receive a weekly digest of Bonsai space options

Send a weekly list of available Bonsai spaces to support infrastructure planning and region reviews.

View example

Check a Bonsai space path every week

Verify that a critical Bonsai space path still returns metadata on a weekly schedule.

View example

Archive a monthly Bonsai space inventory

Create a monthly report of available Bonsai spaces for capacity and regional planning history.

View example

Attach Bonsai cluster context to an incident request

Retrieve a cluster's details when a 0CodeKit incident workflow sends a Bonsai context request.

Supported Triggers and Actions

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

0CodeKit triggers

Bonsai actions

Recurring trigger

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

TriggerScheduled

Get Bonsai Cluster Details

Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.

ActionInstant

Webhook trigger

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

TriggerInstant

List Bonsai Spaces

Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.

ActionInstant

Retrieve Space Details

Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.

ActionInstant

List Spaces

Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.

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.