Keep follow-up table discovery focused on a key Notion page
For a launch plan or operating page, comments can carry important decisions. Pair them with the table list for the connected Baserow workstream.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
List Tables in Database
This tool lists all tables within a specified baserow database. it allows users to retrieve information about all tables in a database by using the get /api/database/{database id}/tables/ endpoint. the expected output is an array of table objects containing details such as id, name, order, database id, type, and first row header.
Why this helps
Workspace-wide notifications are easy to tune out, while a key page deserves a focused follow-through cue.
- Limit the trigger to comments on a specified Notion page.
- Get tables from the relevant Baserow database in the run report.
- Keep a key discussion from fading into general workspace activity.
Setup
Build it in a few focused steps.
- 1Connect Notion and Baserow to Notis once and note the key Notion page and relevant Baserow database.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Use one prompt: When a comment is added to this Notion page, list tables in my relevant Baserow database and remind me to review the discussion.
- 4Select New Comment and scope it to the specified page; choose a run-report channel.
- 5Save and test with one real comment on that page.
Questions about this workflow
How is this different from a workspace-wide comment trigger?
New Comment is for a specified block or page, while Comment Created can listen more broadly.
Does it summarize the whole discussion?
Ask Notis to include available event context. The Baserow action is limited to listing tables.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Baserow. A trigger fires from one place; an action lands in another.
Notion triggers
Baserow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Databases
This tool retrieves a list of all databases in a specified workspace. as a fundamental operation, it allows users to discover which databases are available in their baserow workspace. this operation is independent and requires only authentication in order to fetch essential metadata for subsequent operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Tables in Database
This tool lists all tables within a specified baserow database. it allows users to retrieve information about all tables in a database by using the get /api/database/{database id}/tables/ endpoint. the expected output is an array of table objects containing details such as id, name, order, database id, type, and first row header.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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 Baserow, 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 Baserow.