Bring current Bonsai options into new infrastructure plans
A newly drafted infrastructure page can prompt a fresh spaces list, so planning starts with the options available to your account.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
List Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.
Why this helps
Planning pages are often drafted before someone remembers to check what infrastructure options are available.
- Provides current space availability at the start of planning.
- Helps reduce a separate lookup and context switch.
- Makes options easier to review alongside the new Notion page.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bonsai to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in a conversation.
- 3Give Notis one plain-language instruction to list available Bonsai spaces when an infrastructure planning page is created and summarize them for review.
- 4Select Page Created as the trigger, choose a channel for run reports, and test with one real planning page.
Questions about this workflow
Does every new Notion page need to start this workflow?
Describe the relevant infrastructure pages in the instruction so Notis can decide which new pages call for a lookup.
Which Bonsai information will it return?
It returns a list of available spaces, as provided by the listed Bonsai action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bonsai. A trigger fires from one place; an action lands in another.
Notion triggers
Bonsai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Bonsai Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve Space Details
Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.
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.
List Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.
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 Bonsai, 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 Bonsai.