Keep Baserow options handy when a new intake item arrives
Give incoming requests a simple destination-discovery cue. Notis can list the Baserow databases you may want to review for the next step.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
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.
Why this helps
Intake adds decisions to an already busy queue, and checking existing workspace options can slip behind the first response.
- Tie a new intake item to a quick workspace inventory.
- Keep Baserow choices visible while triaging the request.
- Avoid a separate manual lookup during intake.
Setup
Build it in a few focused steps.
- 1Connect Notion and Baserow to Notis once.
- 2Create an automation for the Notion intake database.
- 3Write one prompt: When a new page is added to this Notion intake database, list available Baserow databases and report them as existing destinations to review.
- 4Select New Page scoped to the intake data source and choose a run-report channel.
- 5Save and test with one real intake item.
Questions about this workflow
Will this route an intake item to a Baserow database?
No. It provides a list of databases for a person to review.
Can I limit reports to my intake database?
Yes. The New Page trigger can be scoped to a Notion data source.
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.