Connect new Notion views to Databox setup
Create a Databox data source when a new Notion view signals a new way of organizing work.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
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.
Why this helps
A new view can reflect a new reporting need, but setting up a destination is easy to defer amid other work.
- Create a visible reporting setup step when views are added.
- Reduce the mental checklist for expanding reporting.
- Give new work views a possible Databox destination.
Setup
Build it in a few focused steps.
- 1Connect Notion and Databox to Notis once in the portal.
- 2Create an automation and use one plain-language instruction to create a Databox source for relevant new Notion views.
- 3Select the Notion View Created trigger and choose a channel for run reports.
- 4Create one test view and verify that the intended Databox source is created.
Questions about this workflow
Should every new Notion view create a source?
The trigger fires workspace-wide. Describe the relevant view types or purposes in the instruction.
Does this connect the view's rows to Databox?
This action creates a data source container. Pushing records requires a dataset and a data push action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Databox. A trigger fires from one place; an action lands in another.
Notion triggers
Databox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Dataset
Tool to delete a dataset by ID in Databox. Use when you need to permanently remove a dataset. This operation is irreversible.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
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.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.