Refresh your Baserow database inventory when Drive files appear
When a new Drive file appears, list the databases in your Baserow workspace so you can review available places to track it.
When something happens in Google Drive, Notis takes the next step in Baserow. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a comment is added to a Google Doc, Sheet, or Slide.
Do this · Action
Retrieves application entries as database metadata, including workspace IDs.
When a new Drive file appears, list the databases in your Baserow workspace so you can review available places to track it.
When a Drive file or folder gains sharing permissions, list tables in your chosen Baserow database for a quick review of available tracking destinations.
A new Docs, Sheets, or Slides comment prompts Notis to list your Baserow databases, helping you decide whether the discussion needs tracking.
When a Drive file's content or metadata changes, list the tables in a selected Baserow database to support a focused tracking review.
On a schedule you choose, retrieve your Baserow database list as a lightweight reminder of where work can be tracked.
At a recurring time, list the tables in a selected Baserow database so your tracking options stay easy to review.
Start a Notis webhook when another process or a manual request needs the current list of databases in your Baserow workspace.
Use an HTTP request to start a Notis lookup of tables in a specified Baserow database, making the directory available when needed.
Notis builds workflows that link Google Drive to Baserow. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieves application entries as database metadata, including workspace IDs.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Creates a user and initial workspace with a database; can also generate authentication tokens.
Fires when a comment is added to a Google Doc, Sheet, or Slide.
Creates up to 200 table rows in one request without triggering row-created webhooks.
Fires when a new file is created in Google Drive.
Lists tables in a database with their details.
Fires when a file is moved to trash or permanently deleted in Google Drive.
Runs a builder page data source query and returns its result.
Fires when new sharing permissions are granted to a file or folder.
Updates up to 200 table rows in one request without triggering row-updated webhooks.
Fires when a file’s metadata or content changes in Google Drive.
Runs a published builder page data source and returns its result.
Fires when changes are detected in Google Drive.
Creates a row in a Baserow table.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Google Drive and Baserow, or any other combination from 1,700+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Baserow.