Skip to content
Notis

Set Up a Databox Dataset for Matching Drive Files

Give a newly matched Drive file a ready reporting destination by creating its dataset with the details you provide.

Trigger

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

Action

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.

Why this helps

A new file that meets a reporting query can sit unused while someone manually creates the destination dataset.

  • Start dataset setup when a file matches the configured Drive query.
  • Create a dataset with a provided title, data source ID, and primary keys.
  • Make setup details visible in the run report.

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Databox once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3In one instruction, provide the dataset title, existing Databox data source ID, primary keys, and explain how the matched file informs setup.
  • 4Pick the New File Matching Query trigger and choose where run reports go.
  • 5Test with one real file that matches the query.

Questions about this workflow

Will this create a Databox data source too?

No. Create Dataset requires a data source ID, so the data source must already exist.

Can the file determine primary keys automatically?

Only if the file contains enough reliable information to identify them. Otherwise, specify the primary keys in the instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Google Drive 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

Comment Added (Docs/Sheets/Slides)

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

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

File Created

Triggers when a new file is created in Google Drive.

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

File Deleted or Trashed

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

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

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 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

File Updated

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

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

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Connect any two apps with Notis in the middle.

Google Drive and Databox, 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 Databox.