Connect Google Docs to Botpress
When something happens in Google Docs, 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
Ways Notis can move work from Google Docs to Botpress
Scan Botpress workspaces when a new Google Doc appears
When a new Google Doc is created, have Notis list Botpress workspaces and summarize where the document topic should be routed.
Review Botpress issues when tracked docs change
When documents matching a search query are updated, ask Notis to list Botpress bot issues and connect them to the latest written context.
Pull Botpress conversations after a Google Doc update
When an existing Google Doc changes, list Botpress conversations and summarize threads that need follow-up against the new context.
Run a Botpress issue check when a launch doc is filled
When a configured placeholder disappears from a Google Doc, list Botpress bot issues and summarize launch risks for review.
Audit Botpress conversations when a doc reaches a size threshold
When a Google Doc crosses a word or character threshold, list Botpress conversations and summarize recurring questions for the growing topic.
Triage Botpress issues when a keyword appears in a doc
When a chosen keyword first appears in a Google Doc, list Botpress issues and organize them around the newly flagged topic.
Review Botpress file tags after a document structure change
When a Google Doc gains or loses tables, headers, footers, or images, list Botpress file tags and explain which content labels may need attention.
Check Botpress workspaces when a Google Doc is deleted
When a document is moved to trash, list Botpress workspaces and summarize which workspace may lose important project context.
Scan public Botpress workspaces when a root folder is created
When a new root folder appears in Google Drive, list public Botpress workspaces and identify useful external reference spaces.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Botpress. A trigger fires from one place; an action lands in another.
Google Docs triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete File
Tool to delete a file by its id or key. use after confirming the file exists.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to get details of the authenticated account. use after confirming valid credentials.
New Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
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.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
LIST_CONVERSATIONS
Tool to list all conversations. use when you need to retrieve and page through chat threads.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
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.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
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.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
LIST_PUBLIC_WORKSPACES
Tool to retrieve a list of public workspaces. use when browsing publicly available workspaces before selection.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
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.
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 Docs and Botpress
Connect any two apps with Notis in the middle.
Google Docs and Botpress, 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 Botpress.