Compare purchase options from a Notion update
When a procurement record changes, start a Google Shopping search that helps you revisit the decision with current options.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Search Google Shopping
Search Google Shopping and get products with prices, merchants, ratings, and refinements.
Why this helps
Procurement decisions often linger because the latest requirements and product prices are in different places.
- Tie product research to a procurement record update.
- Gather product and merchant options through Google Shopping.
- Make a changing purchase decision easier to revisit.
Setup
Build it in a few focused steps.
- 1Connect Notion and Litescrape once in the portal.
- 2Create an automation through the portal or by asking Notis to compare products from procurement updates.
- 3Describe in one instruction how an updated record should guide the Google Shopping search.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test by updating one real procurement record.
Questions about this workflow
What data can Google Shopping return?
The action can return products with prices, merchants, ratings, and refinements.
Can this run only for procurement changes?
The trigger can be scoped to a data source or page. Describe the intended scope when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Litescrape. A trigger fires from one place; an action lands in another.
Notion triggers
Litescrape actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search DuckDuckGo Maps
Search DuckDuckGo Maps for places inside a viewport rectangle or around a center.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Google Shopping
Search Google Shopping and get products with prices, merchants, ratings, and refinements.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search Google Maps
Search Google Maps places in a viewport, or resolve one exact place by id.
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 App Store Reviews
Read Apple App Store reviews for an app in one storefront country, page by page.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search Bing
Run a Bing web search and get organic results, knowledge cards, and paging.
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.
Get Maps Posts
Get the posts a business has published on its Google Maps listing.
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 Litescrape, 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 Litescrape.