Connect One drive to Bonsai

When something happens in One drive, 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 One drive to Bonsai

View example

Check Bonsai spaces when a new runbook arrives

When a new OneDrive runbook is created, list available Bonsai spaces and summarize where the runbook work could fit.

View example

Review a Bonsai cluster after architecture docs change

When an architecture document changes in OneDrive, retrieve a Bonsai cluster detail report and highlight anything worth checking.

View example

Inventory Bonsai spaces when a OneDrive folder is created

When a new OneDrive folder is created for a project, list Bonsai spaces and return a compact inventory for planning.

View example

Capture cluster context when a OneDrive file is deleted

When a OneDrive file is deleted, retrieve specified Bonsai cluster details and summarize the operational context for review.

View example

Check Bonsai space details after a document move

When a OneDrive document is moved or renamed, retrieve the requested Bonsai space details and summarize the impact of the location change.

View example

Add cluster context to recurring OneDrive item changes

When an existing OneDrive item is modified, retrieve Bonsai cluster details and produce a concise change review note.

View example

Review cluster details when a file version is created

When a specified OneDrive file gets a new version, retrieve Bonsai cluster details and summarize what deserves a review.

View example

Review Bonsai space context after sharing changes

When OneDrive sharing permissions change, retrieve Bonsai space details and summarize the access change for a quick review.

View example

Check Bonsai space readiness from a webhook

When your system sends a webhook, list Bonsai spaces and return a readiness summary for the supplied project context.

Supported Triggers and Actions

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

One drive 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

Onedrivebasetrigger

Base trigger for OneDrive changes using Gmail-style state management. Subclasses override `filter_changes(...)` to extract only the relevant items.

TriggerPolling

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

OneDrive File Created Trigger

Triggers when a new file is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.

TriggerPolling

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

File Updated

Trigger that fires when a OneDrive file's content or metadata changes. Returns file ID, last modified time, and modifier info.

TriggerPolling

OneDrive Folder Created Trigger

Triggers when a new folder is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.

TriggerPolling

OneDrive Item Deleted Trigger

Triggers when a file or folder is deleted in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.

TriggerPolling

Item Moved or Renamed

Triggers when a file or folder is moved to a different path or renamed in OneDrive. Includes both old and new path/name data in the payload.

TriggerPolling

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.