Connect Google Drive to Botpress

When something happens in Google Drive, Notis takes the next step in Botpress. 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 Google Drive to Botpress

View example

Check Botpress issues after a Drive comment

When a teammate comments on a Drive document, check the selected Botpress bot for reported issues and send a concise run report.

View example

Review Botpress conversations when a Drive file arrives

When a new Drive file is created, retrieve Botpress conversations and summarize the chat context you ask Notis to look for.

View example

Review Botpress workspaces after a Drive share

When Drive permissions are added, list Botpress workspaces so you can review workspace access and context alongside the sharing event.

View example

Check Botpress file tags after a Drive update

When a Drive file changes, retrieve Botpress file tags and receive a compact inventory in the run report for the review you specify.

View example

Review Botpress conversations after a Drive deletion

When a Drive file is trashed or deleted, retrieve Botpress conversations for the context you specify and summarize the results in a run report.

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Botpress. A trigger fires from one place; an action lands in another.

Google Drive triggers

Botpress actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Delete File

Tool to delete a file by its id or key. use after confirming the file exists.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Account

Tool to get details of the authenticated account. use after confirming valid credentials.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

LIST_BOT_ISSUES

Tool to list issues associated with a specific bot. use when you need to discover errors or configuration problems tied to a bot, optionally paginating through results.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

LIST_CONVERSATIONS

Tool to list all conversations. use when you need to retrieve and page through chat threads.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

LIST_FILE_TAGS

Tool to list all tags used across all bot files. use when you need to retrieve or display file tag metadata; supports pagination via nexttoken.

ActionInstant

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.

TriggerPolling

LIST_FILE_TAG_VALUES

Tool to list all values for a given file tag across all files. use after determining the tag name; supports pagination via nexttoken.

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

LIST_PUBLIC_WORKSPACES

Tool to retrieve a list of public workspaces. use when browsing publicly available workspaces before selection.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

LIST_WORKSPACES

Tool to retrieve a list of workspaces. use when you need to list and page through your botpress workspaces, optionally filtering by handle.

ActionInstant

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.