Turn Ready Booking Content into a Widget
When you finish revising a booking page in Notion, ask Notis to create the corresponding Bookingmood widget.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Booking Widget
Tool to create a new booking widget. use after preparing widget parameters.
Why this helps
Content work and booking setup often happen in different sessions, leaving a finished page without a booking path.
- Connect content completion to a concrete booking setup action.
- Avoid keeping a separate mental reminder to create the widget.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bookingmood once in Notis.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Describe in one instruction how Notis should use the updated booking-page content when creating a Bookingmood widget.
- 4Pick Page Content Updated, choose where run reports go, and test on one real page.
Questions about this workflow
Does every content edit have to create a widget?
Describe the intended readiness condition in the prompt and scope the trigger to the relevant page or data source when setting it up.
Can the content itself guide the widget request?
Yes. The plain-language prompt can ask Notis to use the page content as context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bookingmood. A trigger fires from one place; an action lands in another.
Notion triggers
Bookingmood actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Booking Widget
Tool to create a new booking widget. use after preparing widget parameters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Booking Details
Tool to delete booking details matching given filters. use after confirming which booking detail records to remove.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Organizations
Tool to list organizations. use when you need to retrieve all organizations accessible by the current api key.
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 Booking Widgets
Tool to list booking widgets. use when you need to fetch available widget configurations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Deprecated: Search availability
Deprecated: replaced by search availability.py
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.
Update Booking Details
Tool to update existing booking detail records. use when modifying guest-filled form fields for bookings matching specific filters.
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 Bookingmood, 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 Bookingmood.