Check Apaleo property counts on a schedule
Get a small, repeatable portfolio pulse without adding another manual check to your week.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Return total count of properties
Return total count of properties<br>you need to be authorized (no particular scope required)
Why this helps
A basic count can be easy to forget, leaving founders to reconstruct portfolio changes from memory.
- Make portfolio size easy to check regularly.
- Reduce the work needed for a lightweight status update.
- Use run reports as a record of each scheduled check.
Setup
Build it in a few focused steps.
- 1Connect Apaleo to Notis once.
- 2Create a scheduled automation in the portal or ask Notis to set one up.
- 3In one plain-language prompt, ask Notis to retrieve the total count of Apaleo properties and report the result.
- 4Choose the recurring schedule and a channel for run reports.
- 5Run a test and verify the count is clear.
Questions about this workflow
Can I use this for a weekly pulse?
Yes. Select a weekly recurrence that fits your review routine.
Does the count tell me which properties changed?
The action returns a total count. Use the property roster action if you need the list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apaleo. A trigger fires from one place; an action lands in another.
Notion triggers
Apaleo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a property
Use this endpoint to archive an existing live property this operation set the isarchived flag to true<br>you must have at least one of these scopes: 'properties.manage, setup.manage'.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check if a property exists
Check if a property exists by id.<br>you need to be authorized (no particular scope required)
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Check if a unit attribute exists
Check if a unit attribute exists<br>you must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
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.
Check if a unit exists
Check if a unit exists by id.<br>you must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Check if a unit group exists
Check if a unit group exists by id.<br>you must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
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.
Clones a property
Use this call to clone a specific property. this operation creates a new property with inventory and rate plans from the specified property.<br>you must have at least one of these scopes: 'properties.create, setup.manage'.
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.
Create a unit
Use this call to create a new unit.<br>you must have at least one of these scopes: 'units.create, setup.manage'.
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.
Create a unit attribute
Use this call to create a new unit attribute.<br>you must have at least one of these scopes: 'unitattributes.create, setup.manage'.
Connect any two apps with Notis in the middle.
Notion and Apaleo, 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 Apaleo.