Keep order item research close to investigation notes
When investigation notes change, have Notis retrieve order items so you can continue the review without another search detour.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
List All Order Items
Tool to list all order items. use when you need a paginated list of order items, optionally filtered by order, product, or variant.
Why this helps
Order investigations lose momentum when the order contents require a separate manual lookup.
- Refresh item details during an active investigation.
- Reduce repetitive navigation between notes and order records.
- Keep the lookup aligned with the investigation context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lemon Squeezy once.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one instruction to retrieve relevant Lemon Squeezy order items when investigation notes are edited.
- 4Choose the Page Content Updated trigger and a channel for reports.
- 5Test by updating one investigation page and reviewing the returned items.
Questions about this workflow
Does this change an order?
No. It retrieves order item details.
Can it focus on a particular order?
The action supports an optional order filter. Explain the investigation context in your prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lemon squeezy. A trigger fires from one place; an action lands in another.
Notion triggers
Lemon squeezy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use after verifying the store exists and you need to add a customer to it. example: "create a customer john doe with email johndoe@example.com in store 1."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List All Affiliates
Tool to list all affiliates. use when you need to retrieve affiliates with optional filters and pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List All Checkouts
Tool to list all checkouts. use when you need a paginated list of checkouts, optionally filtering by store or variant.
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 All Customers
Tool to list all customers. use when you need a paginated list of customers with optional filters.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List All Discount Redemptions
Tool to list all discount redemptions. use when you need a paginated list of discount redemptions, optionally filtering by discount or order.
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 All Discounts
Tool to list all discounts. use when you need a paginated list of discounts after confirming authentication.
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 All License Key Instances
Tool to list all license key instances. use when you need a paginated list of license key instances, optionally filtering by license key id.
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.
List All Order Items
Tool to list all order items. use when you need a paginated list of order items, optionally filtered by order, product, or variant.
Connect any two apps with Notis in the middle.
Notion and Lemon squeezy, 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 Lemon squeezy.