Connect One drive to Bench

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

View example

Pause after a benchmark input upload

Add a short Bench pause whenever a new benchmark input file lands in OneDrive, giving sync and indexing time to finish.

View example

Pause after a benchmark file update

Pause briefly when a benchmark dataset or configuration file changes in OneDrive so Bench processes the settled version.

View example

Pause for new benchmark folder indexing

Give OneDrive time to index a newly created benchmark folder before Bench-related processing continues.

View example

Pause after a benchmark artifact is deleted

Pause after a OneDrive benchmark artifact is deleted so Bench consumers have time to observe the removal consistently.

View example

Pause after a benchmark path change

Add a delay after a benchmark file or folder is moved or renamed so Bench references can catch up with the new path.

View example

Pause after an existing benchmark item changes

Sleep after an existing OneDrive benchmark file or folder is modified, separating real edits from new item creation.

View example

Pause after a benchmark version is created

Add a Bench pause when a specified OneDrive benchmark file receives a new version, allowing version metadata to settle.

View example

Pause after benchmark sharing changes

Pause when sharing permission is added or removed on a OneDrive benchmark asset, allowing access changes to propagate.

View example

Pause after a OneDrive benchmark change is detected

Use the base OneDrive change trigger to insert a general Bench pause whenever monitored benchmark content changes.

Supported Triggers and Actions

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

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

Onedrivebasetrigger

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

TriggerPolling

OneDrive File Created Trigger

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

TriggerPolling

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.