Connect One drive to Byteforms
When something happens in One drive, Notis takes the next step in Byteforms. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from One drive to Byteforms
Turn a new OneDrive file into a Byteforms intake form
When a new file appears in OneDrive, create a Byteforms intake form based on its purpose and contents.
Review Byteforms responses after a OneDrive document update
When a OneDrive file changes, retrieve related Byteforms responses and summarize what needs attention.
Create a feedback form for every new OneDrive folder
When a OneDrive folder is created, create a Byteforms feedback form for the work it will contain.
Clean up a Byteforms form when its OneDrive source is deleted
When a source file is deleted from OneDrive, remove the Byteforms form that was created for it when the match is clear.
Fetch the form linked to a moved OneDrive file
When a OneDrive item is moved or renamed, retrieve its related Byteforms form so the workflow context stays current.
Digest Byteforms responses when a OneDrive item is modified
When an existing OneDrive item is modified, retrieve relevant Byteforms responses and produce a focused digest.
Check Byteforms responses after a new OneDrive version
When a new version of a specified OneDrive file appears, retrieve responses for the related Byteforms form.
Inventory Byteforms forms after a OneDrive sharing change
When sharing permission changes on a OneDrive item, list Byteforms forms so you can review access related workflows.
Turn an incoming webhook request into a Byteforms form
Start a Notis webhook with a plain language request and create the requested Byteforms form.
Supported Triggers and Actions
Notis builds workflows that link One drive to Byteforms. A trigger fires from one place; an action lands in another.
One drive triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
Onedrivebasetrigger
Base trigger for OneDrive changes using Gmail-style state management. Subclasses override `filter_changes(...)` to extract only the relevant items.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
OneDrive File Created Trigger
Triggers when a new file is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
File Updated
Trigger that fires when a OneDrive file's content or metadata changes. Returns file ID, last modified time, and modifier info.
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
OneDrive Folder Created Trigger
Triggers when a new folder is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
OneDrive Item Deleted Trigger
Triggers when a file or folder is deleted in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
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.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect One drive and Byteforms
Connect any two apps with Notis in the middle.
One drive and Byteforms, 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 Byteforms.