Review availability when maintenance dates change
Update a maintenance page in Notion and have Notis check Lodgify availability for the affected property and dates.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Get Property Availability
This tool retrieves the availability information for a specific property. it requires the propertyid as an input. the response will include an array of availability objects, each containing the date, availability status, number of units available, price (amount and currency), minimum and maximum nights for booking, and any associated reservation ids for that date.
Why this helps
Maintenance timing and booking availability can be hard to keep in view at the same time.
- Bring availability into a maintenance review without a separate manual search.
- Spot dates that may need closer booking review.
- Keep operational notes and the lookup prompt in the same workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lodgify to Notis once through the portal.
- 2Create an automation prompt to use an updated maintenance page to retrieve Lodgify availability for the named property and affected dates.
- 3Select the Notion Page Updated trigger for the maintenance page or its parent.
- 4Choose a channel for run reports and test with one real maintenance update.
Questions about this workflow
Will it block dates for maintenance?
No. The available action reads availability and cannot block dates or change a property's calendar.
What information should the note contain?
Include the property and the dates you want Notis to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lodgify. A trigger fires from one place; an action lands in another.
Notion triggers
Lodgify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Countries
Tool to retrieve all available countries. use when you need to populate country selectors with supported iso codes and names.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Property Availability
This tool retrieves the availability information for a specific property. it requires the propertyid as an input. the response will include an array of availability objects, each containing the date, availability status, number of units available, price (amount and currency), minimum and maximum nights for booking, and any associated reservation ids for that date.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Channel Connections
Tool to retrieve a list of all channel connections. use when you need to display or synchronize channel connections across properties.
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 Channel Mappings
Tool to list channel mappings. use when you need to retrieve all channel mappings, optionally filtered by property, channel code, or external id. supports pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Channel Reservations
Tool to list channel reservations. use when you need to retrieve reservations across channels filtered by property, channel, or date range.
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.
List Channels
Tool to retrieve a list of all channels. use when you need to view or process all channel configurations.
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.
List Properties
Tool to retrieve a paginated list of properties. use when you need to view or process all properties with pagination.
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 Lodgify, 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 Lodgify.