Connect Notion to Bookingmood
When something happens in Notion, Notis takes the next step in Bookingmood. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Bookingmood
Create a booking widget for a new rental
Turn a new Notion rental listing into a Bookingmood booking widget so launch setup has a clear next step.
Update booking details from a Notion change
When a relevant Notion page changes, have Notis update matching Bookingmood booking details from the revised information.
Review available widgets for a new booking setup
When a Notion setup page is created, have Notis list Bookingmood widgets so you can check what is already available.
Create a widget when booking-page content is ready
Use a Notion page-content update as the cue to create a Bookingmood widget for a prepared booking experience.
Review widgets when a Notion setup status changes
When a Notion setup status changes, have Notis retrieve Bookingmood widgets for a focused review.
Turn a booking comment into a detail update
Use a Notion comment requesting a booking correction to prompt an update to matching Bookingmood details.
Bring widget context into a booking discussion
When a new comment appears on a booking page, have Notis list Bookingmood widgets for the discussion.
Prepare a booking widget for a new space
When a new space record is added to Notion, prompt Notis to create its Bookingmood widget.
Clean up booking details after a confirmed cancellation
Use a confirmed cancellation change in Notion to prompt removal of matching Bookingmood booking details after a clear record check.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Bookingmood
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.