Skip to content
Notis

Give new Notion databases a Grist tracking counterpart

A new Notion database can trigger a simple setup routine that creates a Grist table for the reporting work you describe.

Trigger

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.

Action

Create Table

Tool to create tables in a document. Use after confirming the document ID. Creates one or more tables with specified columns in the given document.

Why this helps

Starting a new database can leave supporting operational tracking undefined until someone remembers to set it up.

  • Make table setup part of a repeatable database launch routine.
  • Reduce the mental checklist for new tracking initiatives.
  • Create a clear reporting destination where useful.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Grist to Notis once through the portal.
  • 2Create an automation prompt describing the Grist table to create when a relevant Notion database is created.
  • 3Choose Database Created as the trigger and describe how Notis should recognize relevant creations.
  • 4Select where run reports should go and test with one intentional database creation.

Questions about this workflow

Does this fire when a data source is added to an existing database?

No. Database Created covers the database container; adding a data source has its own trigger.

Can one trigger create several tables?

Describe the intended table setup in the prompt and keep the result focused on the database workflow you need.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Grist. A trigger fires from one place; an action lands in another.

Notion triggers

Grist actions

Recurring trigger

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

TriggerScheduled

Add Records

Tool to add records to a specified table in a Grist document. Use after confirming doc and table IDs.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document

Tool to create a document in a workspace. Use when you need to add a new document programmatically after selecting a workspace.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create SCIM User

Tool to create a new SCIM user. Use when provisioning new user accounts via SCIM. Run after gathering all required user details.

ActionInstant

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.

TriggerInstant

Create Table

Tool to create tables in a document. Use after confirming the document ID. Creates one or more tables with specified columns in the given document.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Create Document Webhook

Tool to create a new webhook for a specified document. Use when you need to register webhook endpoints for document events in Grist. Run after confirming document ID.

ActionInstant

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.

TriggerInstant

Delete Attachment

Tool to delete a specified attachment from a Grist document. Use when you need to remove a file by providing its document and attachment IDs.

ActionInstant

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.

TriggerInstant

Delete Column

Tool to delete a column from a Grist document table. Use after confirming document, table, and column IDs.

ActionInstant

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.

TriggerInstant

Delete Grist Table Records

Tool to delete records from a specified Grist table. Use when you need to remove specific rows by their IDs. Use after confirming the row IDs exist.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Grist, 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 Grist.