Keep a property page's research moving as it changes
When details shift within a focused property page, Notis can use the latest context to search LoopNet again.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Search commercial listings
Access LoopNet's commercial real estate data programmatically. Search listings by location, property type, and transaction type; retrieve full listing details including pricing and property facts; and find and profile commercial real estate brokers.
Why this helps
Changes inside a page can be easy to miss when they do not appear as a database property update.
- React to changes in the page's working notes.
- Keep a focused research page connected to fresh listings.
- Avoid relying on memory to restart exploration after edits.
Setup
Build it in a few focused steps.
- 1Connect Notion and LoopNet to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to search LoopNet when blocks change in a chosen property page.
- 3Describe in one plain-language instruction how the page content should guide the search.
- 4Choose Notion's Page Updated trigger for the specified page and select a report channel.
- 5Edit a real block on the page and inspect the search.
Questions about this workflow
Which changes start this workflow?
Page Updated fires when any block within the specified Notion page is updated.
Can it follow one active opportunity?
Yes. Select the relevant page for the trigger and describe how Notis should interpret its content for LoopNet.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to LoopNet. A trigger fires from one place; an action lands in another.
Notion triggers
LoopNet actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get broker profile
Access LoopNet's commercial real estate data programmatically. Search listings by location, property type, and transaction type; retrieve full listing details including pricing and property facts; and find and profile commercial real estate brokers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search brokers
Access LoopNet's commercial real estate data programmatically. Search listings by location, property type, and transaction type; retrieve full listing details including pricing and property facts; and find and profile commercial real estate brokers.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search commercial listings
Access LoopNet's commercial real estate data programmatically. Search listings by location, property type, and transaction type; retrieve full listing details including pricing and property facts; and find and profile commercial real estate brokers.
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.
Get commercial listing detail
Access LoopNet's commercial real estate data programmatically. Search listings by location, property type, and transaction type; retrieve full listing details including pricing and property facts; and find and profile commercial real estate brokers.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 LoopNet, 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 LoopNet.