Connect Google Drive to Chatbotkit
When something happens in Google Drive, Notis takes the next step in Chatbotkit. 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 Chatbotkit
Turn new Drive files into chatbot review briefs
When a new Drive file appears, send its available details to a Chatbotkit conversation and ask for a concise review brief.
Ask Chatbotkit to help resolve Drive comments
Turn a new Docs, Sheets, or Slides comment into a focused request for a suggested response or next step in Chatbotkit.
Review new Drive sharing with Chatbotkit
When a Drive file or folder gets new sharing permissions, ask a Chatbotkit bot to summarize the available change details for review.
Check the impact of deleted Drive files
When a Drive file is trashed or deleted, ask Chatbotkit to help assess the change using event details and context you provide.
Summarize meaningful Drive file updates
Ask Chatbotkit to summarize a Google Drive file update and call out a next step in a conversation you specify.
Find Chatbotkit conversations related to Drive changes
When Drive detects changes, retrieve Chatbotkit conversations so you can review whether the event connects to ongoing discussion.
Review conversations when Drive finds a matching file
When a new Drive file matches your trigger query, retrieve Chatbotkit conversations for a quick context check.
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Chatbotkit. A trigger fires from one place; an action lands in another.
Google Drive triggers
Chatbotkit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Complete Conversation
Tool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Integration
Tool to create a new integration. use when you need to set up a support channel integration for a bot after collecting the integration details.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Skillset
Tool to create a new skillset. use when you need to group multiple skills into a single reusable unit.
File Created
Triggers when a new file is created in Google Drive.
List Bots
Tool to retrieve a paginated list of all bots. use when you need to browse or manage multiple bots, and iterate pages via cursor.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
List conversation messages
Tool to list messages in a conversation with pagination. use after obtaining a conversation id to fetch messages page by page.
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.
List Conversations
Tool to retrieve a paginated list of conversations. use when you need to page through conversation history.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
List Datasets
Tool to list datasets. use when you need to browse or paginate through available datasets.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
List Integrations
Tool to retrieve a list of trigger integrations. use when you need to browse or manage configured trigger integrations and iterate pages via cursor.
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 Chatbotkit
Connect any two apps with Notis in the middle.
Google Drive and Chatbotkit, 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 Chatbotkit.