Fetch Booqable order context for Notion booking questions
Keep a booking question from becoming a search task. When someone comments on its page, Notis can fetch the linked Booqable order for context.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Get Order
Tool to retrieve a specific order by id. use when you need complete details of a known order, including optional relationships like customer or coupon. call after confirming the order id.
Why this helps
Questions in a shared booking page can stall while someone searches for the current order details.
- Bring order details into the discussion workflow.
- Reduce delays caused by locating the right rental record.
- Use the booking page as the natural place to ask for context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Booqable to Notis once through the portal.
- 2Create an automation in Automations or ask Notis to set it up conversationally.
- 3In one instruction, tell Notis to fetch the Booqable order ID recorded on the booking page whenever that page receives a comment.
- 4Select Notion's New Comment trigger for the relevant page or block and choose where run reports should be sent.
- 5Test by adding a comment to a page with a known order ID.
Questions about this workflow
Is this different from a workspace-wide comment trigger?
New Comment is for a specified Notion block or page, while Comment Created can fire for comments across the accessible workspace.
Does the comment need to contain the order ID?
The page can contain the ID; the instruction tells Notis to retrieve the order referenced by the page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Booqable. A trigger fires from one place; an action lands in another.
Notion triggers
Booqable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use when onboarding a new client and you have verified their details. example: create 'jane doe' with email jane@doe.com.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Order
Tool to create a new order. use after collecting valid customer id and timing details. example: create an order for customer '297f2584-...' starting at '2018-01-01t09:00:00z'.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Product Group
Tool to create a new product group in booqable. use when you have defined the group's name and pricing details and want to organize items under a shared group.
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.
Delete Customer
Tool to delete (archive) a customer by id. use after confirming the customer should be hidden from searches.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Order
Tool to delete (archive) an order by id. use when you need to hide completed or canceled orders from active listings.
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.
Delete Product Group
Tool to delete a product group by id. use when you need to permanently remove a product group from your catalog after confirming its identifier.
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.
Get Customer
Tool to fetch a specific customer by id. use after obtaining a customer identifier to retrieve full customer details.
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.
Get Customers
Tool to retrieve a list of customers. use when you need to paginate through customers.
Connect any two apps with Notis in the middle.
Notion and Booqable, 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 Booqable.