Review existing discounts during promotion planning
As promotion details change in Notion, Notis can retrieve the current Loyverse discount list for quick review.
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
List Discounts
Tool to list discounts. use when fetching a paginated set of discounts for display or sync.
Why this helps
Promotion planning slows down when you have to leave the brief to confirm which discounts already exist.
- Makes existing discounts easier to review during planning
- Reduces repeat searches for discount details
- Keeps campaign decisions connected to the brief
Setup
Build it in a few focused steps.
- 1Connect Notion and Loyverse to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Write a single instruction asking Notis to retrieve Loyverse discounts relevant to an updated promotion page and summarize potential matches.
- 4Select Notion Page Properties Updated as the trigger and choose a channel for run reports.
- 5Test with one real promotion update and confirm the results are useful.
Questions about this workflow
Does the workflow activate a discount?
No. It retrieves existing discounts for planning and review.
Can I trigger it only for promotion pages?
Choose the promotion data source when selecting the Notion properties trigger, if available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Loyverse. A trigger fires from one place; an action lands in another.
Notion triggers
Loyverse actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Supplier
Tool to create a new supplier. use when you need to register a supplier in loyverse before purchases.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Category
Tool to delete a single category by id. use when you need to remove an unused or deprecated category.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Supplier
Tool to delete a specific supplier by id. use after confirming the supplier id to remove an existing supplier.
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 Category
Tool to get a single category by id. use when you need to fetch details of an existing category in loyverse.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Discount
Tool to get a single discount by id. use after confirming the discount id to retrieve its details.
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 Employee
Tool to get a single employee by id. use after confirming the employee id to fetch its details.
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 JWKS
Tool to fetch json web key set for openid connect. use when verifying loyverse id token signatures.
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 Merchant Info
Tool to get merchant information. use after authenticating to retrieve merchant account details.
Connect any two apps with Notis in the middle.
Notion and Loyverse, 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 Loyverse.