Connect Google Docs to Databox

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

View example

Turn a Google Docs Metric Spec into a Databox Dataset

Create a Databox dataset when you draft a new Google Doc that defines the metrics, fields, and unique keys for a reporting data source.

View example

Keep Databox KPI Definitions Current from Google Docs

When a matching KPI document is created or updated, extract its defined metric records and push them to a Databox dataset.

View example

Send Completed Forecast Assumptions to Databox

When a forecast template's configured placeholder is filled, extract its completed assumptions and push them to a Databox dataset.

View example

Capture Launch Milestones Mentioned in Google Docs

When a configured launch keyword first appears in a Google Doc, extract the specified milestone details and push a record to Databox.

View example

Log Long-Form Research Document Metrics in Databox

When a research document reaches a chosen word or character threshold, summarize its specified metadata and push a record to Databox.

View example

Record Google Docs Structure Changes in Databox

When a monitored document gains or loses structural elements, push a concise record of the observed change to Databox.

View example

Refresh Databox Records from Updated Operating Notes

When an existing Google Doc is modified, extract agreed operating metrics or status fields and push the update to Databox.

View example

Remove a Databox Dataset When Its Spec Is Deleted

When a Google Doc used as a reporting specification is moved to trash, delete the corresponding Databox dataset by its supplied ID.

Supported Triggers and Actions

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

Google Docs triggers

Databox actions

Recurring trigger

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

TriggerScheduled

Create Dataset

Tool to create a new dataset in Databox data source. Use when you need to initialize a dataset with a title, data source ID, and primary keys for unique record identification.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Data Source

Tool to create a new data source in Databox. Use when you need to create a logical container for datasets within a Databox account. Requires accountId, title, and timezone parameters.

ActionInstant

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.

TriggerPolling

Delete Dataset

Tool to delete a dataset by ID in Databox. Use when you need to permanently remove a dataset. This operation is irreversible.

ActionInstant

Document Deleted

Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.

TriggerPolling

Delete Data Source

Tool to delete a data source by ID in Databox. Use when you need to permanently remove a data source. This operation is irreversible and will delete all associated datasets.

ActionInstant

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.

TriggerPolling

Get Dataset Ingestion Status

Tool to check the status of a specific data ingestion for a dataset. Use when you need to verify whether a data ingestion was successful by providing the dataset ID and ingestion ID returned from the initial POST request.

ActionInstant

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.

TriggerPolling

List Accounts

Tool to retrieve all Databox accounts accessible to the authenticated user. Use to identify account IDs required for subsequent API operations like data source creation.

ActionInstant

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

TriggerPolling

Push Data to Dataset (V1)

Tool to push data points to a Databox dataset using the v1 API. Use when you need to ingest data records into a specific dataset by providing the dataset ID and an array of records matching the dataset schema.

ActionInstant

Document Updated

Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.

TriggerPolling

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.