Connect Google Drive to Basin
When something happens in Google Drive, Notis takes the next step in Basin. 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 Google Drive to Basin
Turn a new Drive brief into a Basin intake form
Create a Basin form when a new Google Drive brief arrives, so a project request can move into a consistent intake flow.
Add a Basin webhook after a Drive comment requests it
Use a new comment on a Drive document to prompt Notis to add a callback webhook to the relevant Basin form when its form ID and callback URL are supplied.
Refresh Basin integration settings from an updated Drive spec
When a Drive specification changes, use its latest content as context for updating a Basin form webhook integration.
Notify a Basin destination when a Drive file is shared
When a Drive file receives new sharing permissions, prompt Notis to create a Basin notification webhook for form submissions to an explicitly supplied destination.
Review Basin submissions when a matching Drive file arrives
Use a new Drive file matching a provided query to prompt Notis to fetch submissions for a specified Basin form for review.
Remove a Basin webhook when its Drive source is retired
When a source file is trashed or deleted, prompt Notis to remove the corresponding Basin form webhook using its confirmed webhook ID.
Audit Basin form webhooks after Drive changes
When Google Drive reports changes, prompt Notis to retrieve the webhooks for a specified Basin form so you can review whether its integrations match current documentation.
Get a scheduled inventory of Basin forms
On a recurring schedule, fetch the Basin forms list and send a concise inventory to your Notis report channel.
Review Basin projects on a schedule
Fetch your Basin projects on a recurring schedule and receive a compact review of the project inventory.
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Basin. A trigger fires from one place; an action lands in another.
Google Drive triggers
Basin 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 in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
File Created
Triggers when a new file is created in Google Drive.
Create Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Delete Form
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Delete Integration
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Delete Project
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete Webhook
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
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 Google Drive and Basin
Connect any two apps with Notis in the middle.
Google Drive and Basin, 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 Basin.