Make new project brief links ready to pass along
Add a subpage under a project hub and get a short link for its long URL from L2s.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Shorten URL with L2S
Tool to shorten a given long url. use when you need a concise link representation.
Why this helps
New project briefs often create a follow-up task to tidy links before sharing them with collaborators.
- Make new briefs easier to pass between collaborators.
- Handle link prep at the same moment the subpage appears.
- Keep the result available in your run-report channel.
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 desired workflow to Notis.
- 3Use a single instruction to shorten long URLs on new subpages beneath the selected project page with L2s.
- 4Choose the Notion Page Added to Page trigger for the project parent and select a run-report channel.
- 5Test by adding a project subpage that contains a long URL.
Questions about this workflow
Does this watch nested descendants at every depth?
The trigger is for a new subpage under the specified parent page.
Can it shorten several URLs?
Describe the expected result in the instruction; the L2s action is for shortening a given long URL.
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.