Refresh link inventory context during review
Change the review status in Notion and get an updated list of shortened URLs from L2s.
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 Shortened URLs
Tool to list all shortened urls. use after user authentication to retrieve the user's urls with pagination details.
Why this helps
A review can begin with stale context when the current link inventory is not gathered at the right time.
- Gather fresh list context when a review status changes.
- Reduce the manual start-up steps for link review.
- Include pagination information for larger inventories.
Setup
Build it in a few focused steps.
- 1Connect Notion and L2s to Notis once through the portal.
- 2Create an automation in the portal or describe the workflow to Notis conversationally.
- 3Give one instruction to list the current L2s shortened URLs when the designated inventory page's properties change, and report the results.
- 4Select the Notion Page Properties Updated trigger for the inventory page and choose a run-report channel.
- 5Test by changing a property on the inventory page.
Questions about this workflow
Can the page property update limit the run?
The trigger can be scoped to a page; the prompt can ask Notis to act only for the intended inventory review.
Does the action return link analytics?
No. The listed action returns the user's shortened URLs with pagination details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to L2s. A trigger fires from one place; an action lands in another.
Notion triggers
L2s actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get URL Details
Tool to retrieve details of a shortened url. use when you need metadata about a specific shortened link. use after obtaining a valid url id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Settings
Tool to retrieve current user's settings. use after authentication to fetch email, notification, and appearance preferences.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Shortened URLs
Tool to list all shortened urls. use after user authentication to retrieve the user's urls with pagination details.
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.
Shorten URL with L2S
Tool to shorten a given long url. use when you need a concise link representation.
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 L2s, 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 L2s.